If the 802.1x RADIUS server's certificate is signed by a root authority that the client already trusts (i.e., already has a root certificate, such as from thawte or verisign), then that's correct - you need only supply the users with usernames and passwords, and they're set to go.

However if you are using self-signed certificates, you will still need to distribute your own root certificate to your clients.

- mike

Hi Mike,

Is it true that with 802.1x, the PEAP and CHAP v2
server (with AES WPA2), the client no longer needed to
have CA certification installed on its system as
802.1x and WPA used to?  IF yes, then it must be much
simpler, because, we can just provide username and
password to user.

Thanks,
Timolthy

-- I found this info on technet cableguy ---

" PEAP Support in Windows
PEAP with MS-CHAP v2 is provided with Windows XP SP1,
Windows XP SP2, and Windows 2000 SP4 as part of
enhanced EAP and IEEE 802.1X support. This allows
Windows XP SP1, Windows XP SP2, and Windows 2000 SP4
wireless clients to use PEAP with MS-CHAP v2 for
secure wireless access—with passwords rather than
certificates. ....

PEAP with MS-CHAP v2 requires certificates on the IAS
servers but not on the wireless clients. ...."




_______________________________________________
BAWUG's general wireless chat mailing list
[unsubscribe] http://lists.bawug.org/mailman/listinfo/wireless

Reply via email to