Early Impacts of Let's Encrypt

Re:Early Impacts of Let's Encrypt by jonlucc on Saturday February 20, 2016 @03:03PM (#11141669)

There were free options. I think the biggest benefits to Let's Encrypt are the EFF's clout and the simplicity.

[ Parent | on HN ]

Re:Early Impacts of Let's Encrypt by toyg on Saturday February 20, 2016 @03:09PM (#11141699)

No there were not. Free options meant untrusted certificates or short-lived certificates that could not be renewed.

LE made SSL free, trusted and long-term. You could have made it twice as hard to do the initial setup and people would have jumped at the opportunity regardless.

[ Parent | on HN ]

Re:Early Impacts of Let's Encrypt by pfg on Saturday February 20, 2016 @03:16PM (#11141742)

StartSSL and WoSign have been offering free, publicly trusted certificates with one year lifetimes (and the ability to renew for free) for quite some time.

The former doesn't allow commercial usage, while the latter operates in China. That's probably why it wasn't an option for a lot of people. (That, and the terrible UX at least in StartSSL's case.)

[ Parent | on HN ]

Re:Early Impacts of Let's Encrypt by _ak on Saturday February 20, 2016 @04:58PM (#11142146)

StartSSL isn't free. They charge for certificate revocation.

[ Parent | on HN ]

Re:Early Impacts of Let's Encrypt by beefhash on Sunday February 21, 2016 @01:31AM (#11143575)

Furthermore, their free certificates cannot be used for commercial purposes.

[ Parent | on HN ]

Re:Early Impacts of Let's Encrypt by mehrdada on Sunday February 21, 2016 @04:13AM (#11143879)

I don't know why your comment is downvoted -- this is acutally a legitimate issue mentioned in their terms of service.

[ Parent | on HN ]

Re:Early Impacts of Let's Encrypt by nailer on Sunday February 21, 2016 @08:21AM (#11144388)

StartSSL generally don't mention their terms, so a lot of the use of 'StartSSL Free' is commercial. People don't like to hear they've been misled (and shoot the messenger).

[ Parent | on HN ]

Re:Early Impacts of Let's Encrypt by vsl on Monday February 22, 2016 @04:27AM (#11149601)

They actually started policing this and refuse to renew a certificate if they decide it's a commercial use. Happened to me and rather than argue with them (it wasn't), I bought a $5 one at ssls.com...

[ Parent | on HN ]

Re:Early Impacts of Let's Encrypt by mehrdada on Sunday February 21, 2016 @04:10AM (#11143875)

While I agree LetsEncrypt is awesome, the certificates are actually shorter-lived (90 days), I believe, than the former CAs that issued certs for free (e.g. StartSSL) that offered a year of validity. The rationale is replacing the keys sooner since you can easily do it automatically with LE.

[ Parent | on HN ]

Re:Early Impacts of Let's Encrypt by IgorPartola on Saturday February 20, 2016 @03:09PM (#11141700)

I used to use Wossl and StartSSL before for lots of little personal projects. I recently switched everything over to LE. I am looking forward to switching other projects to it too, such as ones for clients where we had to pay for wildcard certs in the past. Not having to mark the calendar to renew certs every year is going to be really nice.

Incidentally, does anyone have a good way to integrate LE with EC2's load balancers?

[ Parent | on HN ]

Re:Early Impacts of Let's Encrypt by iancarroll on Saturday February 20, 2016 @04:11PM (#11141982)

Amazon operates a free CA (Amazon Certificate Manager) for use with ELB and CloudFront.

[ Parent | on HN ]