Phoronix reports the Mozilla Security Engineering team is planning to make their browser useless for browsing much of the World Wide Web, by deprecating insecure HTTP.
Richard Barnes of Mozilla writes:
In order to encourage web developers to move from HTTP to HTTPS, I would like to propose establishing a deprecation plan for HTTP without security. Broadly speaking, this plan would entail limiting new features to secure contexts, followed by gradually removing legacy features from insecure contexts. Having an overall program for HTTP deprecation makes a clear statement to the web community that the time for plaintext is over -- it tells the world that the new web uses HTTPS, so if you want to use new things, you need to provide security.
See also this document outlining the initial plans.
(Score: 2) by urza9814 on Wednesday April 15 2015, @03:24PM
A forum is a great example of something which *really* ought to be encrypted. Sure, maybe the posts on the forums aren't that important, but what about protecting the users? What about the guy who's using the same password for your forum as he is for his email? You are transmitting his password in plaintext and he probably assumes it's secure. If he's using public wifi then congratulations -- your lax security just got one of your users hacked. And they don't even know how.
It shouldn't cost $10/month to add SSL. I've got SSL on two websites right now and I haven't paid a dime for it. You can probably get a year free from your domain registrar or web host; if not there's StartSSL, there's self-signed certs, and there will soon be Let's Encrypt. Or you could just pay for the cert -- if your host/registrar wants $10/*month* for that, you need to find a new one. Should be $15/year at most. Try Gandi.net maybe. And it shouldn't take more than a few minutes to get the cert installed and configured. SSL isn't just for major corporations; it's cheaper than the cheapest web hosting, and it's just as easy to get configured.