Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Announcing Free and Automated SSL Certs

blog.heroku.com

Post reply on HN
Print view View original

71–79 of 79 posts

Re: Announcing Free and Automated SSL Certs

#71

Post by malka »

Karunamon wrote: post #22
kevindong wrote: post #21

Earlier quoted context omitted.

They are offering SSL free to all free dynos under the .herokuapp.com" rel="nofollow">https:// .herokuapp.com domain. If they offered free SSL for custom domains too, what's the incentive to upgrade to a paid dyno for applications that don't require a large amount of resources? To be fair to Heroku, they have the right to make a profit. As is, it's amazing that they offer a fully free tier. If you don't like their po…

If they offered free SSL for custom domains too, what's the incentive to upgrade to a paid dyno for applications that don't require a large amount of resources? This is exactly my point. The fact that companies are still bucketing "SSL" into "things we can charge extra for" rather than "things that should be the absolute minimum we provide" is irresponsible. Plaintext on the public internet needs to go away in whole.

you dont pay for SSL in this case. SSL is free. You pay for SSL on your domain. You can have SSL for free, if you let heroku advertise through your URL. Seems like a fair deal.

Re: Announcing Free and Automated SSL Certs

#75

Post by nailer »

RKearney wrote: post #67
Nadya wrote: post #19

Earlier quoted context omitted.

Companies who aren't in the business of selling TLS [0] certs themselves have little excuse to not offer free TLS via Let's Encrypt. It's an advantage over any competitors who haven't set that process up. If your company does hosting - your company should provide TLS certs via Let's Encrypt automatically . [0] Can we start dropping the SSL part now? Generally SSL v2/v3 is disabled so it is all over TLS anyway.

> Can we start dropping the SSL part now? Generally SSL v2/v3 is disabled so it is all over TLS anyway. It's the same certificate though. So can we start calling them X.509 certs which is more proper than SSL or TLS cert?

A bunch of folks have started calling the ones used for websites 'https certs' since 'https' actually appears in the browser UI and 'tls/ssl' is unwieldy.
Post reply on HN