Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Recommending GCM for interoperability #174

Open
yaronf opened this issue Jan 31, 2017 · 2 comments
Open

Recommending GCM for interoperability #174

yaronf opened this issue Jan 31, 2017 · 2 comments

Comments

@yaronf
Copy link

yaronf commented Jan 31, 2017

Sec. 18.5.2: the algorithm list includes AES-CBC but not AES-GCM. We think it is time to make the switch, or at least to add GCM as mandatory to implement. Given the audience of this API, the advantage of GCM is that it can be used securely by mere mortals who do not understand the subtleties of integrity protection.

@jimsch
Copy link
Collaborator

jimsch commented Jan 31, 2017

You are a bit late with this - it would need to be addressed in the next version of the specification as I understand how the W3C process works.

@yaronf
Copy link
Author

yaronf commented Jan 31, 2017

Understood. I made these comments during the voting process in December, and was told to post them publicly now, for review when the next version comes along.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants