Re:Apple releases OS X Mavericks 10.9.2 with SSL fix
by nsxwolf on Tuesday February 25, 2014 @04:04PM
(#7300485)
What stops someone from doing that anyway, with their own hot spot, and just serving a self-signed certificate? Will the browser remember the old certificate, and put up the warning?
Re:Apple releases OS X Mavericks 10.9.2 with SSL fix
by danudey on Tuesday February 25, 2014 @04:14PM
(#7300555)
A self-signed certificate will throw an error in the browser because the certificate chain isn't trusted (even if you have the appropriate key).
In SSL, you have the certificate and the key; the key is private and secret, and the certificate is public. A public certificate which is wrong (e.g. self-signed) does you no good because browsers won't trust it (and many of them have made it frustrating to try to bypass the warning).
This isn't true of home networks using PSK, where the AP and the client need an identical PSK in order to authenticate each other. Yes, each other - if you successfully connect to an AP using a PSK, you can be pretty sure that AP knows the same key, and probably isn't someone impersonating it (note however that anyone with the PSK can impersonate the access point).
Remember kids, when you connect to a network without a PSK or more elaborate authentication where you verify the identity of the AP, you generally have no idea who is operating that network.