News for hackers. Stuff that matters.
Re:Launching in 2015: A Certificate Authority to Encrypt the... by Aardwolf on Tuesday November 18, 2014 @10:41AM (#8624288)
My website only contains publically available stuff for people to read.

Is there any reason why I would want to use https for this use case?

Or what does "entire web" mean?

Re:Launching in 2015: A Certificate Authority to Encrypt the... by overshard on Tuesday November 18, 2014 @10:50AM (#8624363)
If you're not using HTTPS it is trivial for anyone in the middle of the "client to server and back" connection to change any of the content.

If you use HTTPS you prevent alterations to that traffic and people receive exactly what you expect they should receive.

Examples of recent ISP misbehaving on non-https websites just 25 days ago on HN: https://news.ycombinator.com/item?id=8500131

Note that the Verizon issue isn't anything entirely content altering but someone who lives in a country with strict monitoring of traffic could easily change the wording of your website to match their propaganda if you aren't using HTTPS.

So yes, your content is publicly available free stuff and no one is probably sending you user login credentials or credit cards but it still matters.

Re:Launching in 2015: A Certificate Authority to Encrypt the... by hughes on Tuesday November 18, 2014 @10:46AM (#8624336)
Only with https could you be sure that your visitors are viewing the exact information you published, and that the content has not been hijacked.

Over http it could conceivably have malicious or tracking content introduced without your knowledge.

Re:Launching in 2015: A Certificate Authority to Encrypt the... by grey-area on Tuesday November 18, 2014 @11:56AM (#8624808)
Is there any reason why I would want to use https for this use case?

Yes it can help you stop:

ISPs inserting adverts into your content (this has happened)

Governments censoring your content or rewriting it

Governments putting people in jail for reading your publicly available (in your country) content, which is illegal in theirs

People impersonating your website

But if you don't want to use it, that's cool too. I suspect all websites will be encrypted at some point soon though, the disadvantages are getting less and less important.

Re:Launching in 2015: A Certificate Authority to Encrypt the... by pbhjpbhj on Tuesday November 18, 2014 @12:26PM (#8624984)
>Governments putting people in jail for reading your publicly available (in your country) content, which is illegal in theirs //

How does that work, surely the gov can still see people accessing the information by monitoring network traffic and the info itself is still public. HTTPS doesn't encrypt the actual request traffic does it, and in any case the gov would still see which server the traffic is going to unless you're using something like tor [and possibly still then].

Re:Launching in 2015: A Certificate Authority to Encrypt the... by tlb on Tuesday November 18, 2014 @12:50PM (#8625139)
HTTPS does encrypt both request and response.

However, you can figure out what pages on a large public site like Wikipedia people are reading over HTTPS, based on statistical traffic analysis, because you can see the size of the request, page, and each of the images. Combined with link following analysis, you can make a fairly accurate guess as to what people are reading.

Re:Launching in 2015: A Certificate Authority to Encrypt the... by desdiv on Tuesday November 18, 2014 @02:38PM (#8625844)
I believe that the combination of HTTP/2 and TLS length-hiding makes that attack impractical. Though admittedly we're still years away from widespread deployment of those two technologies.
Re:Launching in 2015: A Certificate Authority to Encrypt the... by hdevalence on Tuesday November 18, 2014 @12:45PM (#8625109)
There's a difference between

"User X browses Wikipedia"

and

"User X browses Wikipedia articles about topics A, B, C"

where topics A, B, C could be anything user X doesn't want people recording them reading about: for instance, various political articles, articles about mental illness, articles about LGBT issues, etc. Fill in the blanks.

Re:Launching in 2015: A Certificate Authority to Encrypt the... by schoen on Tuesday November 18, 2014 @01:16PM (#8625312)
I use this example myself quite a bit, although we've also got to figure out the distinguishability from page sizes issue. Different Wikipedia pages are different sizes, and they're still different sizes when they're encrypted.

One interesting idea I heard from someone recently is tuning compression so that you target a small number of total page sizes -- rather than padding to expand pages to the same sizes, just don't compress them all quite as well as you could have.

Re:Launching in 2015: A Certificate Authority to Encrypt the... by desdiv on Tuesday November 18, 2014 @01:58PM (#8625604)
I use this example myself quite a bit, although we've also got to figure out the distinguishability from page sizes issue. Different Wikipedia pages are different sizes, and they're still different sizes when they're encrypted.

Both GnuTLS[1] and Nginx[2] have length hiding implemented. But AFAIK OpenSSL doesn't have it yet, so most users are still left in the dark.

[1]http://www.manpagez.com/info/gnutls/gnutls-3.2.10/gnutls_180...

[2]http://nulab-inc.com/blog/nulab/securing-nginx/

Re:Launching in 2015: A Certificate Authority to Encrypt the... by schoen on Tuesday November 18, 2014 @02:10PM (#8625670)
Thanks, I didn't realize that process was so far along!

It might still be challenging to get large sides to adopt padding that will increase the amount of traffic they send (of course, the idea of reducing the efficiency of compression has the same net effect). But it's great to know that there's already a tool in place for traffic padding, at least in some implementations.

Re:Launching in 2015: A Certificate Authority to Encrypt the... by eyeface on Tuesday November 18, 2014 @10:49AM (#8624355)
Sure! If I trust your site but not my ISP, then https allows me to trust the connection between us. That means that nobody can tamper with the content and inject some malicious JS. Also, the ISP could only tell that I am talking to your server, and not anything beyond that.
Re:Launching in 2015: A Certificate Authority to Encrypt the... by aw3c2 on Tuesday November 18, 2014 @10:44AM (#8624316)
Yes, because it is no one's business what people are looking at anyways. If you have more than one URL, HTTPS will hide that.

HTTPS will also make an attacker unable to change your content.

Re:Launching in 2015: A Certificate Authority to Encrypt the... by sp332 on Tuesday November 18, 2014 @11:02AM (#8624452)
Anyone along the way (like an ISP) could inject things into your webpage. Like ads https://arstechnica.com/tech-policy/2013/04/how-a-banner-ad-...
Re:Launching in 2015: A Certificate Authority to Encrypt the... by pencilcode on Tuesday November 18, 2014 @10:47AM (#8624338)
People could think they are reading an article from your site but actually they're not or the text was tampered with. With https you ensure people are actually reading what you published.
Re:Launching in 2015: A Certificate Authority to Encrypt the... by kstrauser on Tuesday November 18, 2014 @01:06PM (#8625246)
Honestly, you're probably not going to get a large personal benefit from this. The larger good is that you'll be helping move the Internet toward encrypted-by-default, which is an enormous societal benefit.

Like you, I don't host any private or remotely sensitive information. I'm encrypting my site because I think it's the right thing to do, even though there's little personal return on investment.