-
Notifications
You must be signed in to change notification settings - Fork 29.6k
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
Support Let's Encrypt in core #9244
Comments
Can you come up with a more concrete implementation proposal than "let's do it"? I'll add the feature-request label. |
When doing I am not familiar with how letsencrypt works internally, so I cannot give any technical details. The reason I created this issue is that I am not very familiar with how https certification works and I guess most people aren't, too. Mozilla's announcement created complaints that having to obtain a certificate will be hard for small websites and if most people will need it in the future, I think it's important for this process to be simple. |
-1 from me, node core shouldn't be in the business of maintaining SSL certificates. That kind of thing is best left to userland. |
I disagree with this as well. I think Let's Encrypt is great, but in the end it's just regenerating certificates and that can be done with the hundreds of tools already created. |
I think we should put out an official guide in the docs on how to do this with libraries on userland. |
@mcollina As well we could contribute to the certbot website, which has a dropdown supporting different web servers already. |
@PaulBGD yes of course! |
Not going to happen as a feature in core, I added an issue for a guide if anyone has time to work on it: nodejs/docs#117 |
Mozilla annouced their intent to deprecate http over year and a half ago. Chrome plans to limit new features to https and mark http as non-secure. Having a https site will only get more and more important in the future and with browsers pushing https everywhere, I expect it will be essential for most Node users who who run a server.
Native Let's Encrypt support would make the complicated process of getting a certificate super easy.
The text was updated successfully, but these errors were encountered: