"Duane Arnold" <(E-Mail Removed)> wrote in message
news:Xns953F60F1FDA6Cnotmenotmecom@216.148.227.77. ..
> "Jack Dee" <(E-Mail Removed)> wrote in
> news
psce16m1p27azd6@your-vimqhg1d72:
>
> > I have a laptop with 802.11G and want to get a wireless ADSL 'modem'
> > so I can move around the house.
> >
> > I know you can detect a wireless LAN in the area, even if it's
> > secured, but could anyone pinpoint its location to my house?
> >
> > I'm thinking about burgulars working out that I have a LAN and then
> > assuming there's mobile equipment ready to carry off in the middle of
> > the night! 
> >
> >
>
> http://www.practicallynetworked.com/...ess_secure.htm
>
> Duane
Although this is a decent article, I have three problems with it:
1) It says don't use TCP/IP for File Sharing. This is good advice if
you're trying to thwart intruders from the Internet, where they must be
coming in via TCP/IP. But despite the articles claim that wireless
intruders must be connecting to you with TCP/IP, it isn't true. They can
use whatever layer-3 protocol they wish. If an intruder runs a sniffer on
your AP, s/he will see what protocols you are using.
2) It says to use WEP for data and authentication. If WPA is not
available, then WEP encryption is a good thing. But WEP authentication is a
bad thing. It was poorly implemented, and it reveals too much about your
keys. You should prefer Open Authentication to Shared Key Authentication.
3) It says "Don't send your ESSID." Aside from the misuse of the term
ESSID, there has been much discussion on this NG about broadcasting SSIDs.
Even proponents of not broadcasting SSIDs admit that it's just weak
"security by obscurity." There are even administrative downsides to hiding
your SSID. If you're using encryption, you have no need to hide your SSID.
Ron Bandes, CCNP, CTT+, etc.