Elliptical ciphers are defined to AT-TLS, but not used

On the AT-TLS (server), the V3CipherSuites4Char parameter was invalidly used to defined a cipher constant. The V3CipherSuites statement must be used to define either a single cipher constant, or a string of one or more 2-hexadecimal character ciphers. The V3CipherSuites4Char statement is used to define a string of one or more 4-hexadecimal character ciphers only.

Because AT-TLS invalidly used the V3CipherSuites4Char parameter to define cipher constants representing elliptical cipher suites, none of those elliptical cipher suite definitions took effect. As a result, the non-elliptical cipher suite offered the client was accepted.

Here is how the TTLSCipherParms statement on the AT-TLS server side needs to be coded to make sure that an elliptical cipher suite is chosen in this case:

 TTLSCipherParms                   cipher1~AT-TLS__Gold                  
     {                                                                       
       V3CipherSuites                        TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 
       V3CipherSuites                        TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 
       V3CipherSuites                        TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384 
       V3CipherSuites                        TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256 
       V3CipherSuites                        TLS_RSA_WITH_AES_256_GCM_SHA384      
       V3CipherSuites                        TLS_RSA_WITH_AES_128_GCM_SHA256  
       V3CipherSuites                        TLS_RSA_WITH_AES_256_CBC_SHA256  
       V3CipherSuites                        TLS_RSA_WITH_AES_128_CBC_SHA256  
       V3CipherSuites                        TLS_RSA_WITH_AES_128_CBC_SHA     
       V3CipherSuites                        TLS_RSA_WITH_3DES_EDE_CBC_SHA    
     }