JSS TLS Socket Cipher Suite Configuration Issue

George Wash <[email protected]>
Newsgroups gmane.comp.mozilla.crypto
Message-ID <CANTk7V7gaCnbXJ11zYZzf-eXj4BQZQu9cbudB9G3B9en8h3aWg@mail.gmail.com>
Hello,

Using NSS 3.19.1-18 & JSS 4.2.6-37 on RHEL7.
When using Mozilla JSS to create a client socket to a TLS server, I've
configured the socket to only use TLS_RSA_WITH_AES_256_CBC_SHA and
TLS_RSA_WITH_AES_128_CBC_SHA.
If I TCP dump the TLS Handshakes in the connection and inspect the cipher
suites presented in the TLS Client Hello, I see that my TLS client is
unconditionally asserting TLS_ECDHE_WITH_AES_256_GCM_SHA384 along with
various flavors of TLS_RSA_WITH_AES_256_X_SHA and
TLS_RSA_WITH_AES_128_X_SHA. Where is the TLS_ECDHE_WITH_AES_256_GCM_SHA384
coming from?

Has anyone seen this behavior before?

Thanks
GW
-- 
dev-tech-crypto mailing list
[email protected]
https://lists.mozilla.org/listinfo/dev-tech-crypto
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.