Re: HTTPS and URL encoding
From: Thor Kottelin (thor_at_anta.net)
Date: 05/27/04
- Next message: Roger Hunt: "Re: Security bug in Winamp"
- Previous message: Big Will: "Re: What is the difference between a worm and a trojan ?"
- Maybe in reply to: Billy Kimber: "HTTPS and URL encoding"
- Next in thread: Barry Margolin: "Re: HTTPS and URL encoding"
- Reply: Barry Margolin: "Re: HTTPS and URL encoding"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Date: Thu, 27 May 2004 23:08:52 +0300
Jason LaRue wrote:
>
> So the shorter answer is:
> Your ISP will see https://www.realsite.com/alk63d1goua8hd...
No. Your ISP will see a TCP connection, an SSL/TLS handshake, and encrypted
stuff from there on. They might also see one or more preceding DNS queries,
which might give away the host name, which, in turn and OTOH, would probably
also be easy to determine by doing a reverse lookup.
Thor
-- http://thorweb.anta.net/ IRCnet #areena
- Next message: Roger Hunt: "Re: Security bug in Winamp"
- Previous message: Big Will: "Re: What is the difference between a worm and a trojan ?"
- Maybe in reply to: Billy Kimber: "HTTPS and URL encoding"
- Next in thread: Barry Margolin: "Re: HTTPS and URL encoding"
- Reply: Barry Margolin: "Re: HTTPS and URL encoding"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Relevant Pages
|
|
