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

Update default SSL/TLS key to support TLS 1.2+ #1371

Closed
wants to merge 1 commit into from
Closed

Update default SSL/TLS key to support TLS 1.2+ #1371

wants to merge 1 commit into from

Conversation

knowledgejunkie
Copy link
Contributor

Summary

This updates the default key used for local HTTPS server testing to
support TLS 1.2+. An RSA key of 4096 bits is created, with SHA256
digest support, with duration and Common Name as before.

Motivation

As of Debian 10 "buster" the default system supported TLS level is 1.2,
and as a result, the current server.crt certificate using RSA:1024 with SHA1
digest support is not supported and will no longer work "out of the box".

With Apple, Google, Microsoft, and Mozilla announcing plans to deprecate
TLS 1.0 and 1.1 in early 2020, and Linux distributions updating their
baseline TLS support, it seems prudent to update this key so that it
continues to work for developers.

References

https://groups.google.com/forum/#!topic/mojolicious/gjz-0uvUDLk
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=929675

This updates the default key used for local HTTPS server testing to
support TLS 1.2+. An RSA key of 4096 bits is created, with SHA256
digest support, with duration and Common Name as before.

As of Debian 10 "buster" the default system supported TLS level is 1.2,
and as a result, the current server.crt certificate using RSA:1024 with SHA1
digest support is not supported and will no longer work "out of the box".

With Apple, Google, Microsoft, and Mozilla announcing plans to deprecate
TLS 1.0 and 1.1 in early 2020, and Linux distributions updating their
baseline TLS support, it seems prudent to update this key so that it
continues to work for developers.
@jhthorsen
Copy link
Member

I'm positive to updating the key to TLS 1.2+, but I'm negative to accept a new cert via a PR from someone who's not in the core team. Please correct me if I'm wrong in considering that a security concern.

@kraih kraih added the bug label Jun 28, 2019
@kraih
Copy link
Member

kraih commented Jun 28, 2019

Agreed, someone from the team has to generate the new cert.

@kraih kraih added the security label Jun 28, 2019
@knowledgejunkie
Copy link
Contributor Author

Ack. Would you like me to close this PR and open a regular issue (with the relevant tags)?

@kraih
Copy link
Member

kraih commented Jun 28, 2019

@knowledgejunkie I suppose that would make sense, thanks.

@kraih
Copy link
Member

kraih commented Jun 28, 2019

Thanks for the report. I've updated the certificate. 59b409c...2343209

@kraih kraih closed this Jun 28, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants