Skip to main content
5 events
when toggle format what by license comment
May 10, 2015 at 8:33 comment added Paŭlo Ebermann Just a technicallity: POP3 is for receiving mail, not for sending. (Though it might use the same password.) Sending is usually done by SMTP.
May 9, 2015 at 6:53 history edited Freedo CC BY-SA 3.0
deleted 7 characters in body
May 9, 2015 at 6:44 comment added cpast That said, you're right that it's not technically impossible to provide encryption on all Wi-Fi; you might not be able to trust that it's not a rogue AP, but you could at least stop others besides the AP from sniffing traffic. You're correct on some of the big reasons it's not done.
May 9, 2015 at 6:41 comment added cpast There are indeed reasons why the X.509 PKI doesn't work for Wi-Fi in general: there is no meaningful way to associate a certificate with a network. To have certificates work, you need a subject name that is globally unique; the DNS provides such a thing, but nothing of the sort generically exists for Wi-Fi (the SSID is not globally unique), so certificates can't generally work there. WPA-Enterprise does use mutual authentication, and some methods (like PEAP) use X.509 to do so (the unique name is the domain name of the RADIUS server), but that doesn't work well for most networks.
May 9, 2015 at 6:02 history answered Freedo CC BY-SA 3.0