> ...but even on your own network, you can't trust wifi... WPA2 Enterprise uses AES for per-client session key generation, and -when you use EAP-TLS or EAP-TTL

> ...but even on your own network, you can't trust wifi... WPA2 Enterprise uses AES for per-client session key generation, and -when you use EAP-TLS or EAP-TTLS- TLS for transportation of client credentials and assurance that both ends of the conversation are who they say they are. [0] You can make WiFi just as secure as wired Ethernet, it just takes a -surprisingly small- bit of work. :) If Windows and Mac machines supported EAP-PWD, or (even better) WFA-TLS-UNAUTH [1] even coffeeshop WiFi would be secure from passive attack. [0] When you use WiFi client and RADIUS server certs, rather than just username and password. [1] EAP offers a very large array of authentication methods. EAP-PWD authenticates with just a username and password and doesn't muck about with TLS certs. WFA-TLS-UNAUTH uses TLS, but doesn't verify the RADIUS server cert and doesn't require a client cert. Both of these schemes offer substantially less assurance than full-blown EAP-[T]TLS, but they also let you offer encrypted WiFi without hassle.