|
|
|
timmmay: Does https hide the URL or does it just encrypt the content of the request/response? I thought the URL was still clear text, but perhaps it creates an encrypted connection with the server then requests the URL.
Anyone with low level access will be able to tell what server you're addressing even if the full URL is hidden.
freitasm: Many years ago my (then) girlfriend looked at my monitor and asked "Are you looking at porn sites?"...
The url was "godaddy.com".
True story.
Twitter: ajobbins
Referral links: Quic Broadband (free setup code: R587125ERQ6VE) | Samsung | AliExpress | Wise | Sharesies
Support Geekzone by subscribing (browse ads-free), or making a one-off or recurring donation through PressPatron.
ajobbins:freitasm: The URL...
Google Images
kyhwana2:
The entire URL is encrypted, other than a DNS request for example.com, all your ISP will see is an encrypted connection on port 443 to whatever IP example.com resolves to.
If they don't check the DNS requests, all they'd see is the IP and you can host multiple domains/websites on a single IP address.
freitasm: Many years ago my (then) girlfriend looked at my monitor and asked "Are you looking at porn sites?"...
The url was "godaddy.com".
True story.


maverick:freitasm: Many years ago my (then) girlfriend looked at my monitor and asked "Are you looking at porn sites?"...
The url was "godaddy.com".
True story.
sure it wasn't whosyourdaddy.com
________
Antoniosk
ajobbins:freitasm: The URL...
Google Images
Referral links: Quic Broadband (free setup code: R587125ERQ6VE) | Samsung | AliExpress | Wise | Sharesies
Support Geekzone by subscribing (browse ads-free), or making a one-off or recurring donation through PressPatron.
Klipspringer:kyhwana2:
The entire URL is encrypted, other than a DNS request for example.com, all your ISP will see is an encrypted connection on port 443 to whatever IP example.com resolves to.
If they don't check the DNS requests, all they'd see is the IP and you can host multiple domains/websites on a single IP address.
The DNS leak is only limited to google chrome and internet explorer. Firefox has the ability to send DNS requests via the proxy. Problem solved :-)
Kyanar:Klipspringer:kyhwana2:
The entire URL is encrypted, other than a DNS request for example.com, all your ISP will see is an encrypted connection on port 443 to whatever IP example.com resolves to.
If they don't check the DNS requests, all they'd see is the IP and you can host multiple domains/websites on a single IP address.
The DNS leak is only limited to google chrome and internet explorer. Firefox has the ability to send DNS requests via the proxy. Problem solved :-)
How is that problem solved? The DNS request is still unencrypted, and still has to pass through the Layer 7 appliances your ISP has, so it can still be read if they had any inclination to. The important thing is that your ISP doesn't have any inclination to.
Klipspringer:
Because the DNS request is sent on the remote side of the connection, not locally.
The DNS request is encrypted just like everything else so your ISP cannot read it. I tested this a while ago using Wireshark. All browsers will leak the DNS requests except for firefox when setup correctly.
More info here on how to enable remote DNS lookups in firefox.
|
|
|