When I see articles about security related topics I immediately expect them to be served over HTTPS and get frustrated when they are not. It makes me think if HN should perhaps make a stand and either display some sort of lock icon next to secure links or make it harder for insecure links to show in the front page. Where is the right place to discuss this?
Why do you need https for text only page? Sure, somebody could do deep packet inspection, but they would not find anything they couldn't find going to the domain (that won't be hidden by https anyway) directly. EDIT: previously incorrectly stated 'url' instead of 'domain'.
How Tor Works
11–20 of 33 posts
Re: How Tor Works
#12Earlier quoted context omitted.
Why do you need https for text only page? Sure, somebody could do deep packet inspection, but they would not find anything they couldn't find going to the domain (that won't be hidden by https anyway) directly. EDIT: previously incorrectly stated 'url' instead of 'domain'.
For integrity, ie. tamper-resistance and knowing if MitM tampering was done.
Re: How Tor Works
#13Earlier quoted context omitted.
Why do you need https for text only page? Sure, somebody could do deep packet inspection, but they would not find anything they couldn't find going to the domain (that won't be hidden by https anyway) directly. EDIT: previously incorrectly stated 'url' instead of 'domain'.
I don't know what is on a page until I visit it, so to make a stand myself in favor of a less insecure internet, I use HTTPS Everywhere in strict mode, which blocks HTTP. I have found that mostly I can live with it, and wish for the community (HN audience is a good part of it) to keep pushing (through a bit of pressure perhaps) towards an HTTPS only internet.
Re: How Tor Works
#14Earlier quoted context omitted.
Why do you need https for text only page? Sure, somebody could do deep packet inspection, but they would not find anything they couldn't find going to the domain (that won't be hidden by https anyway) directly. EDIT: previously incorrectly stated 'url' instead of 'domain'.
But URLs are encrypted as it's the TCP connection that's encrypted, isn't it?!
Re: How Tor Works
#15Earlier quoted context omitted.
For integrity, ie. tamper-resistance and knowing if MitM tampering was done.
What's the end game for our hypothetical man in the middle? To edit the article to be subtly incorrect, so you'll misunderstand how Tor works?
Re: How Tor Works
#16Earlier quoted context omitted.
For integrity, ie. tamper-resistance and knowing if MitM tampering was done.
What's the end game for our hypothetical man in the middle? To edit the article to be subtly incorrect, so you'll misunderstand how Tor works?
Re: How Tor Works
#17It would also be useful to point out limitations and vulnerabilities. Tor browser has no protection against malware that hits the Internet directly, bypassing Tor circuits. But Tor Project does not prominently warn users about that on its website. While Tor Project does acknowledge Tor's vulnerability to global adversaries, there's also no prominent warning about that. If you run Tor in a terminal, you see "This is e…
Re: How Tor Works
#18Earlier quoted context omitted.
For integrity, ie. tamper-resistance and knowing if MitM tampering was done.
What's the end game for our hypothetical man in the middle? To edit the article to be subtly incorrect, so you'll misunderstand how Tor works?
A more frequent one is injection of ads or tracking scripts, or 'web accelerators' that recompress images. Certain ISPs have been known to do these.
Re: How Tor Works
#19When I see articles about security related topics I immediately expect them to be served over HTTPS and get frustrated when they are not. It makes me think if HN should perhaps make a stand and either display some sort of lock icon next to secure links or make it harder for insecure links to show in the front page. Where is the right place to discuss this?
Why do you need https for text only page? Sure, somebody could do deep packet inspection, but they would not find anything they couldn't find going to the domain (that won't be hidden by https anyway) directly. EDIT: previously incorrectly stated 'url' instead of 'domain'.
The only thing that's not hidden are the domain names in the certificate that the server presents.
The rest of the URL is encrypted, along with all data and headers.