I highly doubt a company that's running OK today will get shut down by a the $30/month expense equivalent that is a wildcard cert.
Re:Intent to deprecate: Insecure HTTP
by yellowapple on Tuesday April 14, 2015 @10:30PM
(#9378578)
No, but prices will go up. Free tiers will be significantly reduced or outright eliminated. Cheap tiers won't be as cheap anymore. A lot of individuals and small businesses will now suddenly be faced with more costs, and while $30/month might seem small to you, that adds up considerably over several years.
Not everyone on the internet is a multi-millionare YCombinator alumnus.
... Please. You're talking about the difference of a single paid plan or something. There's no viable product or company out there now where $30 a month is even make anyone blink.
Re:Intent to deprecate: Insecure HTTP
by yellowapple on Wednesday April 15, 2015 @05:16PM
(#9384210)
Maybe if the entirety of your perspective comes from massive multi-million-dollar websites. For everyone else (particularly Mom-and-Pop small businesses, individuals trying to sell things online, etc.), that cost can very well be prohibitive, particularly when it dwarfs the costs of site hosting and even the domain name.
I'm talking about the little taqueria across the street from my house. They're perfectly viable, yet are going to be scared off from investing in a cert if it's going to be the single most expensive thing for their online presence. It's these sorts of folks that your argument blissfully ignores.
Many online free hosting sites that give you a subdomain are HTTP only because wildcard HTTPS certs are expensive.
Many of those services would go away or turn paid-only in an HTTPS-only world.
The children of the future have already lost Geocities and dial-in BBSes that we grew up with; how will they manage if their Internet isn't exactly like ours? /s
> If your CPU is really so limited then why are you using HTTP at all? Use a custom binary protocol with or without encryption as appropriate.
I might not want to write the client for said custom binary protocol.
Like it or not, a lot of embedded devices (Arduino, Spark Core) provide libraries for serving JSON over unencrypted HTTP. Restricting yourself to devices that are more powerful (say, Raspberry Pi 2) would require you to use a bigger form factor for the hardware, and/or would cost more.