You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Nov 6, 2023. It is now read-only.
Repository navigation
This repository was archived by the owner on Nov 6, 2023. It is now read-only.
Directory of paid CAs for cases when 90-day certificates are impractical #8186
I think Let's Encrypt is suitable for long-term needs
Only if your current web host offers ACME. Many web hosting subscribers currently subscribe to shared hosting providers and managed VPS providers that do not integrate an ACME client. Because of the 90-day validity period of certificates issued by Let's Encrypt, a subscriber would have to log in every 60 to 90 days and ether upload the renewed certificate to a form in the hosting control panel or file a support ticket with the hosting provider's technical support department. Unlike a certificate from Let's Encrypt, this periodic installation labor cannot "be obtained for free".
I don't think we should recommend any specific paid service
With the distrusting by Mozilla and by Google of WoSign and StartSSL certificates issued on October 21, 2016, or later, all widely trusted certificate authorities that issue TLS certificates with a validity period at least one year are paid services. Some hosting subscribers are willing to pay $15 per three years in order to avoid the periodic labor of having to log in to the panel eighteen times over the course of those three years. Instead of "recommend[ing] any specific paid service", would it be proper to recommend a directory of paid services? Or would it instead be proper to recommend switching from a web hosting provider that does not integrate with Let's Encrypt to one that does?
I just don't see how it's proper to sweep under the rug the addition of a requirement to upload a certificate to your web host six times a year.
Other free or nearly free HTTPS options include GitHub Pages and AWS, but they, like Let's Encrypt, require some compromises. Why does Let's Encrypt get special treatment in the FAQ? I don't know for sure. I do know the EFF is a primary sponsor of Let's Encrypt, and also hosts an ACME client at https://certbot.eff.org. I think it's all right for the EFF to put a little ad in there for their own thing.
I definitely don't want some constantly-shifting list of commercial sites in the FAQ.
I'd be okay with linking to some general, comprehensive "How to configure HTTPS" page that is maintained elsewhere by an organization or person with a mission aligned with the EFF's, maybe the EFF itself, or the FSF or Whisper Systems or Bruce Schneier or something/someone like that.
Activity
jeremyn commentedon Jan 12, 2017
That part of the FAQ is answering the question Isn't it more expensive or slower for a site to support HTTPS compared to regular HTTP? You can think of it as a little advertisement for site admins to use HTTPS, not a walkthrough on how to do it.
Other free or nearly free HTTPS options include GitHub Pages and AWS, but they, like Let's Encrypt, require some compromises. Why does Let's Encrypt get special treatment in the FAQ? I don't know for sure. I do know the EFF is a primary sponsor of Let's Encrypt, and also hosts an ACME client at https://certbot.eff.org. I think it's all right for the EFF to put a little ad in there for their own thing.
I definitely don't want some constantly-shifting list of commercial sites in the FAQ.
I'd be okay with linking to some general, comprehensive "How to configure HTTPS" page that is maintained elsewhere by an organization or person with a mission aligned with the EFF's, maybe the EFF itself, or the FSF or Whisper Systems or Bruce Schneier or something/someone like that.
pipboy96 commentedon Mar 28, 2019
Off-topic, unrelated to the extension.