full-disclosure - Wireless Security

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

From: Simon.Hailstone at orthogonsystems.com (Simon Hailstone)
Subject: Wireless Security

> wireless being used for meeting rooms etc, so the users would be
> random which would mean the constant addition / removal of MACs
> to the AP which would probably not be possible or practical all
> of the time.   Although policy could dictate that when a wireless
> card is given out, the MAC address in added to the AP, however if
> you have multiple APs in different areas of building, being
> administered by different IT depts then this could soon become be
> a problem.

One way around to ease the management burden in this kind of setup
is to have your AP's communicate with either central or distributed
RADIUS servers, in order to determine if specific MAC addresses should
be allowed to associate with the AP.

Actually I'm not sure if you can do this with the Cisco 802.11b kit,
however it is certainly possible with many other vendor's kit.

There is a white paper on this at :

http://www.wi-fitechnology.com/Wi-Fi_Reports_and_Papers/Freeradius_Deploymen
t_of_MAC_Address.html

( http://makeashorterlink.com/?K22A159A6 ) in case it wraps!

Simon Hailstone
Orthogon Systems