Jump to content

Recommended Posts

Posted

Was reading about this in IT Week the other day. Here's a snippet from the cable guy.

 

The upshot in IT Week was that it was OK for heterogenous windows domains but add any other client and you're screwed. If this is the case you should buy a third party tool for managing security.

Posted
The upshot in IT Week was that it was OK for heterogenous windows domains but add any other client and you're screwed.

 

Linux will work ok in a windows domain with WPA2 or WPA2-PSK provided you set it up correctly (Samba, WPA-Supplicant, correct encryption kernel modules, etc). Linux has been able to run WPA2 for some time thanks to work over at the HostAP.

 

One must be careful of which hardware is used. As the MS article points out, some chipsets are incapable of processing WPA2 encrypted data in a timely fashion. Linux has managed to make a few of the older chipsets work (check the hostAP site for a list) because they allow the encryption work to be offloaded to the PC's CPU but its a bit hit and miss generally.

Posted
What I meant was that the article implied that the new systems from Microsoft became a nightmare to configure for multiple types of hardware if you have differetn client-types.
  • 1 year later...

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now



×
×
  • Create New...