News for hackers. Stuff that matters.
Re:Marking HTTP as Non-Secure by jedberg on Saturday December 13, 2014 @02:05AM (#8744487)
> There's no more good reason not to have HTTPS

Cost. Today I host my website for 6 cents a month as a static page on Amazon S3.

To go https, I'd have to first acquire a certificate (lucky that can be free and with Let's Encrypt will be). Then I have to find someone to host that certificate. I can pay someone hundreds to thousands of dollars in setup and monthly fees.

Or, the cheapest option I've found is to get a $6/mo VPS as a frontend, put nginx on it, and put my cert there. The problem is that costs 100 times as much as what I pay now, and I have to maintain a server and it's not served from multiple redundant servers like my site is now.

Or I can use Amazon's free SNI support, making it so that older browsers can't see my site and I have no way of blocking people from using http or redirecting them.

There is currently no good, cheap option to do SSL only that is viewable by everyone.

That's why I haven't switched yet.

Re:Marking HTTP as Non-Secure by unethical_ban on Saturday December 13, 2014 @02:17PM (#8746029)
I understand the principle, but let's not get to philosophical about this: You ran reddit's servers and worked at netflix in their availability department. Cut out a morning coffee and you have enough money to run SSL.

SNI works with anyone on Windows > XP, and any mobile / Apple / Linux OS you'll find visiting your site. How many IE6/XP hits does your site get per month?

Re:Marking HTTP as Non-Secure by bad_user on Saturday December 13, 2014 @03:25PM (#8746284)
Even on Windows XP, it is only IExplorer that doesn't do SNI. Chrome or Firefox have no problem.

The bigger problem right now is Android 2.x. But the lifetime of phones is only about 2 years and the market-share of Android 2.x has dropped below 20%.

And it really depends on the audience. The market share of all IExplorer versions on my blog is less than 4%, out of which IExplorer 11 represents more than half of that.

Re:Marking HTTP as Non-Secure by magicalist on Saturday December 13, 2014 @04:10PM (#8746426)
> The bigger problem right now is Android 2.x. But the lifetime of phones is only about 2 years and the market-share of Android 2.x has dropped below 20%.

Below 10% even[1]. Agreed on device lifetime. Unlike PCs that can stick it out much longer, give it another year and it'll be well below IE6 levels. Can't come soon enough.

[1] https://developer.android.com/about/dashboards/index.html

Re:Marking HTTP as Non-Secure by hayksaakian on Saturday December 13, 2014 @03:09PM (#8746203)
The problem here is that increasing the difficulty or learning curve of a system is always unpopular.

If SSL was truley as trivial as a check box, then we would see very wide adoption.

Re:Marking HTTP as Non-Secure by coldtea on Saturday December 13, 2014 @04:44AM (#8744739)
>The problem is that costs 100 times as much as what I pay now

The "100 times as much" is not that impressive, if it merely goes from 6 cents to 6 dollars.

Re:Marking HTTP as Non-Secure by ctz on Saturday December 13, 2014 @07:41AM (#8745060)
I suggest looking at the world beyond your immediate environs.

6 cents vs 6 dollars is the difference between a person in a low-income economy spending 0.1% vs 18% of their income on a website.

Re:Marking HTTP as Non-Secure by Mister_Snuggles on Saturday December 13, 2014 @11:56AM (#8745576)
That works out to an income of about $33/mo. I think that person has a lot more to worry about than where to host their static site.
Re:Marking HTTP as Non-Secure by ctz on Saturday December 13, 2014 @01:29PM (#8745866)
My source for that figure was the World Bank[1], which gives a GNI per capita of 400USD PA for the Democratic Republic of Congo.

[1]: http://data.worldbank.org/country/congo-dem-rep

Re:Marking HTTP as Non-Secure by egwor on Saturday December 13, 2014 @05:15AM (#8744791)
Which in big chunks of the western world is not that much, but it will increase the barrier for entry for many in poorer nations. For commercial sites, then maybe I see a benefit. For everything else... why bother? The info isn't secret, doesn't need to be and since there's so much data going around already is anyone malicious bothering to look?
Re:Marking HTTP as Non-Secure by tomjen3 on Saturday December 13, 2014 @10:37AM (#8745358)
And what do you think that means for websites that are 100 times as big? They go from being rather cheap to host to being money drains.

We need better infrastructure.

Re:Marking HTTP as Non-Secure by jonny_eh on Saturday December 13, 2014 @03:42AM (#8744625)
Cloudflare provides a free ssl service.
Re:Marking HTTP as Non-Secure by psykovsky on Saturday December 13, 2014 @05:13AM (#8744787)
A free MITM service, you mean.
Re:Marking HTTP as Non-Secure by cmircea on Saturday December 13, 2014 @05:37AM (#8744836)
With ECDSA only certificates, which are even less supported by old browsers than SNI.
Re:Marking HTTP as Non-Secure by bearbin on Saturday December 13, 2014 @04:39AM (#8744720)
NearlyFreeSpeech.net offers comparable value to S3, and you can use apache features like .htaccess for redirection. Only problem is that it's still SNI, if that's important for you.
Re:Marking HTTP as Non-Secure by diafygi on Saturday December 13, 2014 @03:05AM (#8744579)
Sounds like an opportunity for a startup if I've ever heard one.
Re:Marking HTTP as Non-Secure by coldtea on Saturday December 13, 2014 @04:44AM (#8744740)
Yeah, more nickel and diming.