I guess its time for buys those costly VPNs but can we get away with https?
Rapidshare downloads can be HTTPS. Can ISPs snoop that?
|
|
|



Check out my LPFM Radio Station at www.thecheese.co.nz - Now on iHeart Radio, TuneIn and Radio Garden
As per the usual std disclaimer.. "All thoughts typed here are my own."
ZollyMonsta: Put on your tin foil hat and you'll be fine.
Check out my LPFM Radio Station at www.thecheese.co.nz - Now on iHeart Radio, TuneIn and Radio Garden
As per the usual std disclaimer.. "All thoughts typed here are my own."
s26f84:
Rapidshare downloads can be HTTPS. Can ISPs snoop that?
Sales Engineer
Snowflake
www.snowflake.com
about.me/nzregs
Twitter: @nzregs
dclegg:ZollyMonsta: Put on your tin foil hat and you'll be fine.
Just make sure it IS yours. You don't want to get prosecuted for illegal foil sharing.
s26f84: I guess its time for buys those costly VPNs but can we get away with https?
Rapidshare downloads can be HTTPS. Can ISPs snoop that?
Audiophiles are such twits! They buy such pointless stuff: Gold plated cables, $2000 power cords. Idiots.
OOOHHHH HYPERFIBRE!
muppet:
HTTPS is still going to require a DNS lookup though. If you're not tunneling those DNS requests, then your ISP could pickup on the fact you're requesting certain hosts.
Sales Engineer
Snowflake
www.snowflake.com
about.me/nzregs
Twitter: @nzregs
Regs:muppet:
HTTPS is still going to require a DNS lookup though. If you're not tunneling those DNS requests, then your ISP could pickup on the fact you're requesting certain hosts.
i dont think it really matters if the ISP sees you accessing a certain site anyway. the ISP may care if you're using all their bandwidth pool, but beyond that I cant see any reason for them to care.
Regs: the ISP doesnt do the detection/investigation of piracy, they just act on notices sent from the copyright holders. the copyright holders dont get access to ISP logs, or portions of ISP logs without a warrant. the copyright holders cant get a warrant unless they have some sort of evidence of an offence in the first place.
Audiophiles are such twits! They buy such pointless stuff: Gold plated cables, $2000 power cords. Idiots.
OOOHHHH HYPERFIBRE!
the host portion of the url you type in the browser is unencrypted and it has to be, otherwise it would be kind of difficult to reach a host. the GET request and any parameters are encrypted.
Time to find a new industry!
foobar:the host portion of the url you type in the browser is unencrypted and it has to be, otherwise it would be kind of difficult to reach a host. the GET request and any parameters are encrypted.
That is not correct.
Your entire HTTP header (including the Host line) are encrypted with SSL. The issue is that at some point you will have to do a DNS lookup for the name. However, that is a different request and may have happened at any time before the browser attempts the connection. So, if someone can correlate your DNS and HTTP(s) queries ... then, yeah, they know the domain you are accessing. If they only see your SSL traffic, however, then all they see is the IP address you are connecting to. Sadly, in the case of SSL, that is often enough to also arrive at your domain.
foobar:the host portion of the url you type in the browser is unencrypted and it has to be, otherwise it would be kind of difficult to reach a host.? the GET request and any parameters are encrypted.
That is not correct.
Your entire HTTP header (including the Host line) are encrypted with SSL. The issue is that at some point you will have to do a DNS lookup for the name. However, that is a different request and may have happened at any time before the browser attempts the connection. So, if someone can correlate your DNS and HTTP(s) queries ... then, yeah, they know the domain you are accessing. If they only see your SSL traffic, however, then all they see is the IP address you are connecting to. Sadly, in the case of SSL, that is often enough to also arrive at your domain.
?
All comments are my own opinion, and not that of my employer unless explicitly stated.
|
|
|