https - hopefully not too stupid a question
lists at internetpolicyagency.com
Sun Jun 17 16:53:01 BST 2012
In article <4FDDF8D7.7080108 at zen.co.uk>, Peter Fairbrother
<zenadsl6186 at zen.co.uk> writes
>In practice, the client will normally do a DNS on the hostname before a
>https connection is established. So if all the client's traffic is
>being monitored then the monitors will usually have the hostname anyway.
Hmm, if I try to access:
(Where 184.108.40.206 is what my DNS translates www.update.microsoft.com
This is probably not the site you are looking for!
You attempted to reach 220.127.116.11, but instead you actually reached a
server identifying itself as www.update.microsoft.com. This may be
caused by a misconfiguration on the server or by something more
serious. An attacker on your network could be trying to get you to
visit a fake (and potentially harmful) version of 18.104.22.168.
Is this my browser (Chrome) not getting its act together, or is there an
infelicity in one of the protocols?
More information about the ukcrypto