Check for both TLS 1.2 and AES-GCM support in SSLServerSocket tests.
commit299e307c22f01fb6a5e4dc0a3a6dfa0c04b9d1db
authordavidben <davidben@chromium.org>
Mon, 4 May 2015 19:06:49 +0000 (4 12:06 -0700)
committerCommit bot <commit-bot@chromium.org>
Mon, 4 May 2015 19:07:21 +0000 (4 19:07 +0000)
tree6666de3883067c496665e34664eb29096d8fc7d7
parent365d0800c0f214e1b9469e4342f7638fc3ec53f6
Check for both TLS 1.2 and AES-GCM support in SSLServerSocket tests.

This is a speculative fix for crbug.com/484034. It seems NSS added AES-GCM
support before the key derivation steps for TLS 1.2, so there may be versions
of NSS which support the former but not the latter.

BUG=484034

Review URL: https://codereview.chromium.org/1126633002

Cr-Commit-Position: refs/heads/master@{#328164}
net/socket/ssl_server_socket_unittest.cc