Issue metadata
Sign in to add a comment
|
Support AES-256-GCM
Reported by
demioben...@gmail.com,
May 3 2016
|
||||||||||||||||||||||
Issue description
Chrome Version : 50.0.2661.94 (Official Build) (64-bit)
URLs (if applicable) :
Other browsers tested:
Add OK or FAIL, along with the version, after other browsers where you
have tested this issue:
Safari:
Firefox: FAIL
IE:
What steps will reproduce the problem?
(1) Connect to a website over TLS that supports AES-256-GCM as only AEAD
(2)
(3)
What is the expected result?
AES-256-GCM is negotiated
What happens instead?
AES-256-GCM is not negotiated
Please provide any additional information below. Attach a screenshot if
possible.
Some websites need (or think they need) 256-bit connection security, or may be required to have >128 bit security by regulation (not sure if there are any). These should be allowed to use AES-256-GCM, even if it is not preferred. It is still much better than AES-256-CBC and when support for the latter is removed Chromium will not be able to connect to these sites.
,
May 3 2016
|
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by jri@chromium.org
, May 3 2016Owner: davidben@chromium.org
Status: Assigned (was: Unconfirmed)