4 ms·
> Forget security concerns, I'm just appalled that to acceptably do encryption today I need to pay some company! That's wrong. Well, you don't need to pay anyo
by geofft 12y ago
> Forget security concerns, I'm just appalled that to acceptably do encryption today I need to pay some company! That's wrong.
Well, you don't need to pay anyone to do encryption. You do need to do pay people to do identity verification. That's a more-than-pedantic difference, even though encryption without identity verification is generally meaningless.
First off, you're already paying someone to have a domain name. I sorta understand the distaste on principle, but I've never really understood, as a practical matter, why paying $10+/year for a domain name is totally fine, but paying $5/year on top of that for SSL isn't. (And yes, the race-to-the-bottom has hit $5, see ssls.com. This isn't even counting StartCom and the future Let's Encrypt.)
Second, and related to that, what you're paying them for is the human element in key continuity. If you ever lose your key, you're going to want to be able to regain a key for the same website that you've already published everywhere, that everyone already has localStorage for, etc. And be careful about saying that you don't care: Crypto.cat (which, at this point, definitely knows what they're doing) managed to lock themselves out from SSL by requesting a hardcoded public-key pin and then losing all the public keys they'd pinned. This isn't really a risk that you think is realistic until disaster strikes, and the last thing you want in the middle of a disaster is to have to rename your website and convince everyone that they should use the new site.
And the process of maintaining infrastructure to re-provision certificates to people costs money. It's possible that it could be funded in different ways (just like, e.g., all of the work that goes into the browsers themselves is funded in ways that don't involve charging website owners or users). But there is a thing there that involves humans, there are advantages to it involving humans, and humans need to be paid.
- shawabawa3 12y ago> And yes, the race-to-the-bottom has hit $5, see ssls.com What's the race to the bottom for wildcard certs though? Looks like $80+/year, which is frankly completely ridiculous seeing as it's exactly the same amount of work for the CA. The whole thing's a racket, we would honestly be better off using self-signed certs and certificate pinning (perhaps with a global list of cert pins stored in the browser/a server the browser implicitly trusts) I mean, we have to trust the browser anyway, might as well make it handle all the security
- methou 12y agoStartssl has wildcard certs if you buy their service at 50$/yr, plus many other stuff.
- jnky 12y agoThe $59.90 account only buys you identity verification so that you can get a cert for your own personal domains. When you want to get certs for a company's domains, you also have to pay for organisation verification for another $59.50. In neither case are you allowed to request certificates for domains owned by other entities, even if you are authorized to do so by the owner (e.g. as a service provider). See here: https://www.startssl.com/policy.pdf https://www.startssl.com/policy.pdf
- dankohn1 12y agohttps://letsencrypt.com https://letsencrypt.com will be offering free certificates this year and will hopefully completely transform the SSL business. Given that extended validation certificates have little if any consumer value, letsencrypt could quickly take over the whole SSL world.
- sharth 12y agoIt's a dot org: https://letsencrypt.org https://letsencrypt.org
- hobarrera 12y agoStartssl give free certificates, and letsencrypt will be joining the party this year as well.
- nickysielicki 12y agoJust to clarify, when I said "acceptably do encryption" I meant "do encryption without requiring a user to wrestle their browser and install my certificate".
- geofft 12y agoFirefox does opportunistic encryption now. :) http://arstechnica.com/security/2015/04/new-firefox-version-says-might-as-well-to-encrypting-all-web-traffic/ http://arstechnica.com/security/2015/04/new-firefox-version-... It's just that lots of other browsers are hesitant to follow suit, because OE doesn't protect you from most attacks that the average internet user would expect encryption to protect you from (e.g., you shouldn't type credit card numbers into an OE webpage). And even Firefox treats the site as http, not https, although the physical connection is over TLS on port 443. That's what, in the browsers' eyes, is "acceptable" encryption, which is what translates to the user experience of having to override the browsers' warning.