Enhanced WiFi Security Patch For FreeBSD 59
Posted
by
timothy
from the sekrit-treehouse-password dept.
from the sekrit-treehouse-password dept.
Dan writes "Roland van Laar has a new, significant wi-fi patch for FreeBSD 5.1 and higher. The patch, available for download and testing, blocks clients with an empty or 'ANY' ssid and disables ssid broadcasting using the underlying firmware feature. SSID (Service Set ID) is used to identify wireless clients to a wireless / wired gateway. Wireless devices from the same manufacturer generally ship with the same default SSID. A beacon is a type of packet/frame that contains the SSID of a network. It is used to sync clocks on client devices and to make it easy for new network clients to see what networks are available. Preventing others from using your ssid is a means (although not foolproof!) of securing your wireless network."
SSIDs? (Score:2, Interesting)
However, I'm wondering: how much security does SSID-based blocking add (could individuals forge SSIDs, or would they have to be organizations with cash and determination?)? Shouldn't all connections on a wireless network use a strong encoding (SSH or such)?
How do real people provide and use services that are normally insecure (NFS comes to mind) over Wifi?
Re:SSIDs? (Score:5, Informative)
An SSID is just a small text string, typically a short word, used to identify networks. Typically you can ask your PC to list available networks and it'll provide you with a list of SSIDs, the joke being that most of them will have the names "DEFAULT", "BELKIN", etc. You configure your wireless hub to have a particular name, and then you'll be able to easily select yours. If you hide it, as the article suggests (not a particularly original feature, I'd guess most wireless hubs allow you to hide SSIDs, mine does), then it's still useful as you manually can tell your PC which network to connect to (eg enter the name) and it'll still find it despite the fact you've hidden the SSID.
If someone was to try to masquerade their network as yours - say, give their network the same name as yours so that you might connect to it by accident - then they could do so, but any other wireless security you'd have switched on would automatically defeat it (within reason - WEP, for example, is probably the most popular 802.11 security technology, but it's infamously insecure.)
Re:SSIDs? (Score:3, Informative)
The simplest implementation of that is to design your network under the assumption that any Wifi portions are about as secure as the general Internet.
In other words, stick the Wifi network on it's own outside your firewalled "internal" network and use a VPN client to connect your laptop or whatever to the real network. The gateway for the Wifi network would in this case usually be a firewal
Re:SSIDs? (Score:1)
Re:SSIDs? (Score:2)
Then "for home use, no encryption is good enough".
There IS no security in WEP.
Presume it.
It's as secure as leaving your key under the mat and hoping your neighbor doesn't notice (ok break onto my LAN and you don't get much (vs. the house)). But telling people that WEP is "ok" is just irresponsible.
That said, I generally use SSH and the only cleartext on my wireless net is webbrowsing.
OS X, Unix and even that other OS all support IPSec. PPTP is even better.
Bad dot
Re:SSIDs? (Score:1)
Re:SSIDs? (Score:2)
It just sucks when someone with not tons of effort can send a billion spams out your box one afternoon.
Card support? (Score:2)
Re:Card support? (Score:3, Informative)
A step in the right direction (Score:2, Informative)
On a side note, it's a real shame that a useful article has garnered mostly trolls and flamebait as responses. Sigh...
Wireless Leiden - the Why :-) (Score:2)
The issue is that througout the city we have omni antenna's - where -anyone- can associate with - and directional antennas which provide the interlinks between nodes (although the network covers a medium sized city - we use no copper; all interlinks are wireless).
On these interlinks we only want node-to-node traffic.
As the network is totally open (no username, password or any thing) - we hav
I love FreeBSD. (Score:1)
The question beg's to be asked, shouldn't