Replace the TLS_AEGIS_256_SHA384 ciphersuite with TLS_AEGIS_256_SHA512 #104
Conversation
The latest AEGIS draft, as well as the IANA TLS registry have been updated to replace TLS_AEGIS_256_SHA384 with TLS_AEGIS_256_SHA512. This follows the recommendations from [1] for new cipher suites. [1] https://eprint.iacr.org/2023/913.pdf
|
Hi @jedisct1! Thank you for your pull request and welcome to our community. Action RequiredIn order to merge any pull request (code, docs, etc.), we require contributors to sign our Contributor License Agreement, and we don't seem to have one on file for you. ProcessIn order for us to review and merge your suggested changes, please sign at https://code.facebook.com/cla. If you are contributing on behalf of someone else (eg your employer), the individual CLA may not be sufficient and your employer may need to sign the corporate CLA. Once the CLA is signed, our tooling will perform checks and validations. Afterwards, the pull request will be tagged with If you have received this in error or have any questions, please contact us at [email protected]. Thanks! |
|
@mingtaoy has imported this pull request. If you are a Meta employee, you can view this diff on Phabricator. |
Summary: The latest AEGIS draft, as well as the IANA TLS registry [1] have been updated to replace `TLS_AEGIS_256_SHA384` with `TLS_AEGIS_256_SHA512`. This follows the recommendations from [2] for new cipher suites. [1] https://www.iana.org/assignments/tls-parameters/tls-parameters.xhtml#tls-parameters-4 [2] https://eprint.iacr.org/2023/913.pdf X-link: facebookincubator/fizz#104 Differential Revision: D51794472 Pulled By: mingtaoy fbshipit-source-id: 4e2b9f0d374a08d1d40348f2f049c0f7b03f1616
The latest AEGIS draft, as well as the IANA TLS registry [1] have been updated to replace
TLS_AEGIS_256_SHA384withTLS_AEGIS_256_SHA512.This follows the recommendations from [2] for new cipher suites.
[1] https://www.iana.org/assignments/tls-parameters/tls-parameters.xhtml#tls-parameters-4
[2] https://eprint.iacr.org/2023/913.pdf