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 for Android: free password hash cracker in your pocket

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

Message-ID: <B8F58E36-21B9-11D8-B26B-000393594AA0@adotout.com>
From: dopacki at adotout.com (Dennis Opacki)
Subject: Wireless Security

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

The NIST wireless STIG has some good reference information on deploying 
and securing wireless networks.

http://csrc.nist.gov/pcig/STIGs/wirelessstig-v2r1-071003.zip

Regarding registration of MAC addresses, many APs support Radius for 
MAC address authentication. I have seen setups where users are allowed 
to add their card to a radius database via a web form on a corporate 
intranet. As users typically have to authenticate to a corporate 
intranet, this can help tie a specific user to a card MAC address.  
When cross-referenced with the Radius server logs, than can provide 
some semblance of an audit trail.

Note that it would be important to add removal of MAC address 
information to your employee termination checklist.

- -Dennis

On Nov 28, 2003, at 9:40 AM, Patrick Doyle wrote:

> Hope this question isn't off topic,
>
> I am currently looking at securing wireless networks using Cisco 
> hardware and wanted to check what peoples thoughts are on security.
>
> I have read about using LEAP and also IPSEC, my concerns about using 
> LEAP would be that although the client and access point send hashes of 
> the username and password, and also dynamically create WEP keys, the 
> process is still vulnerable to brute force attacks.  Now i know you 
> can lock down the Access Point (AP) to specific MAC addresses, 
> however, in our environment i can see 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.
>
> To me IPSEC looks like be the better solution using SecurID tokens 
> (one time passwords) to authenticate users, any thoughts would be 
> appreciated.
>
>
>
>
>
> BBCi at http://www.bbc.co.uk/
>
> This e-mail (and any attachments) is confidential and may contain 
> personal views which are not the views of the BBC unless specifically
> stated.
> If you have received it in error, please delete it from your system. 
> Do not use, copy or disclose the information in any way nor act in
> reliance on it and notify the sender immediately. Please note that the 
> BBC monitors e-mails sent or received.
> Further communication will signify your consent to this.
>
> _______________________________________________
> Full-Disclosure - We believe in it.
> Charter: http://lists.netsys.com/full-disclosure-charter.html
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (Darwin)

iD8DBQE/x21QiNpn8q9J2DcRAtN0AJwOeYGPY4W5ITE8hakPK7LY/GEqKQCgg9Mz
IEJU1nn7QO2jrvR6xAQorhg=
=Hf1U
-----END PGP SIGNATURE-----