4 ms·
It's hard to complain about a slight deadline miss from an incredible project offering free stuff.
by ocdtrekkie 9y ago
It's hard to complain about a slight deadline miss from an incredible project offering free stuff.
- tyingq 9y agoI am a little worried about the monoculture LE is creating. I don't have any bright and practical ideas to fix that, however. Short of some other consortium making an equivalent, but with different tech underneath.
- marcosdumay 9y agoFor TLS certificate authorities, a monoculture is way better than the alternative.
- tyingq 9y agoI'm thinking of some critical flaw in ACME, or CA outage, bad cert push, etc. I get your point, but I think there's a legit risk here.
- nodesocket 9y agoPrecisely the problem. Real companies mostly prefer to use paid solutions because they have comfort and confidence in knowing there is a business and backing behind it. At least I know I do. I never got the whole developer complex wanting and even expecting everything for free. Seems hypocritical and counter-entrepreneur. Also for what's worth, I've been deploying Let's Encrypt into production recently using Caddy and (on-demand) TLS and while it works, the rate limits being reset weekly is really scary and VERY VERY easy to hit. I know myself and my clients would be willing to pay for Let's Encrypt Pro (higher rate limits, etc). Take our money.
- ocdtrekkie 9y agoThat's not Let's Encrypt's role to play though. As a user, I'd be much more skeptical of an LE cert'd site than a Verisign cert'd site. That's not a knock on LE, that's just recognizing a higher barrier to entry. Let's Encrypt's goal is to get everyone encrypted, not necessarily to ensure everyone is who they say they are. And as a fellow person who does real business at times, I often prefer paid products because I know I can get support from the company backing it. I don't think Let's Encrypt will replace the entire CA industry, and I don't think it should. (As tyingq says, monocultures are bad.)
- BrandoElFollito 9y ago> not necessarily to ensure everyone is who they say they are How does Verizon (to take your example) ensures this? They have the same zero verification process for the non-EV cert.
- ocdtrekkie 9y agoAt bare minimum, getting a cert almost anywhere else requires a credit card.
- BrandoElFollito 9y agoThis is not something which helps to decide whether the target website is what they claim to be. I can use my CC to buy faccebook.com, and I will get it (again, outside of EV). I may then be tracked by Interpol for fraud, but to the end user this does not change anything: Verizon has issued a certificate for my faccebook.com
- ams6110 9y agoIYAM, any major web property such as google, facebook, credit card issuers, etc. should buy up all the most likely typo-ed versions of their domains so that this doesn't happen. The average user is going to blame Facebook anyway if they get duped into logging in at faccebook.com, and it goes to protecting their brand (trademarks are weakened if the owner doesn't defend them).
- BrandoElFollito 9y agoThey do, and if they don't, they end up like the White House a few years ago when whitehouse.<I forgot the TLD> was bought and an almost exact replica was created, according to Rule 34. My point is that you can buy any site from a CA and no verification is done, exactly as with Let's Encrypt. Even with an EV there is no guarantee that the requester is genuine ("best effort" to check)
- cm2187 9y agoFor any medium or large company, the $200-ish cost of a commercial wildcard certificate is a non problem. I think let's encrypt is mostly useful for small businesses and individuals, who can live with these limits.
- Belphemur 9y agoI think it's not the cost the issue, but the peace of mind brought by the automatisation of the process of certificate renewal. This where LE is for me different from usual cert providers.
- cm2187 9y agoTrue but you can buy a 7y commercial wildcard cert. That also offers some peace of mind. You still have to worry about renewing it in many years but on the other side you are not exposed to a job breaking or an api changing.
- tialaramex 9y agoNope. Currently (today, 21 February 2018) the limit is 39 months, starting 1 March 2018 the limit becomes 825 days. These limits are set down in the Baseline Requirements, which are rules agreed between the Certificate Authorities and Browser vendors (in practice mostly OS vendors) at their standing meeting. Chrome at least actually implements these in software, ie leaf certificates which seem to have a longer lifetime are simply invalid and don't work. In practice commercial CAs tend to sell products as 1 year, 2 year or 3 year, and then they use the extra days in the BRs to let you "keep" the extra days if you renew early, so that you don't feel the need to wait until the last minute to renew to get maximum value.
- ams6110 9y agoIf you're in business, you need a process so that you are not likely to forget dates. Tax filing deadlines, other regulatory reporting, etc. Certificate expiration can just be part of that. It's not really that hard. I manage a dozen+ certs manually, I get reminder emails 30 days before they expire, and it takes literally a few minutes to submit a new CSR. I could autmate it even more than I do, but https://xkcd.com/1205/ https://xkcd.com/1205/
- ryanqian 9y agoMe too, the rate limit is preventing me to keep on using LE.
- liveoneggs 9y agothis is the second delay