On Sat, 3 May 2008 21:24:26 -0400, Pete Holland Jr. wrote
(in article
<86d223c4-6472-40e5-81a2-480e08a64671@[EMAIL PROTECTED]
>):
> So, the basic question is, is there a way to secure data transmission
> and receiving? Should he not use anything that doesn't ask for a WPA
> password (no going to Panera Bread or Starbucks)? And, since a
> sidejacker can pick up whatever is being sent, what's to keep them
> from grabbing the WPA password or https encryptions and cracking them
> anyway? Or, is there a book for a wifi security newbie that will help
> clear this stuff up?
All encryption can be broken if you want to put in the required effort.
However, while WEP can be broken in a matter of minutes if not seconds,
WPA
takes hours if not days, so unless a 'sidejacker' really, really, REALLY
wants in, having WPA protection is good enough. Being 'protected' by WEP
is
actually worse than having no protection at all, as it causes hassles for
legitimate users while being nearly transparent to attackers.
I'd start here: <http://en.wikipedia.org/wiki/Wireless_security>
Some of
the
links are useful; others are, well, ****e. This article
<http://www.theregister.co.uk/2007/05/15/wep_crack_interview/>
is a good
overview of the state of WEP, and has some good links.
You might want to look at
<http://www.oreillynet.com/pub/a/wireless/2002/04/19/security.html>
and
<http://safari.oreilly.com/0321136209>.
Warning: this is heavyweight
division
stuff. The first page dates from 2002, and so is somewhat outdated. The
second points to a very large, and somewhat expensive, book which goes
into
excruciating detail about wireless security. That book was first published
in
2003, but has been updated since. Also mentioned on that page is a book on
wireless hacking, which by definition shows how to defend against hack
attempts. Probably the best book for your purposes would be
<http://press.oreilly.com/pub/pr/1912>.
Note that O'Reilly books tend to
be
members of the heavyweight division in more ways than one. The current
edition was released in February 2008, so it's right up to date.
--
email to oshea dot j dot j at gmail dot com.
|
