Re: Proper WEP Code

[Dan Williams <dcbw redhat com>]

On Mon, 2007-12-10 at 08:29 -0600, Aaron Konstam wrote:
> On Sun, 2007-12-09 at 19:22 -0500, Dan Williams wrote:
> > On Sun, 2007-12-09 at 15:48 -0600, Aaron Konstam wrote:
> > > On Mon, 2007-12-10 at 01:42 +1000, nathanael jansons gmail com wrote:
> > > > -----BEGIN PGP SIGNED MESSAGE-----
> > > > Hash: SHA1
> > > > 
> > > > 
> > > > 
> > > > Hey everyone sorry to disturb you all but what is the proper way to put
> > > > your wep code in hex into the nm-applet? So far i can't figure it out
> > > > and it won't allow me to connect. This is my code (obviously without the
> > > > stars):
> > > > 
> > > > 
> > > > **:38:22:05:40:AB:**:EF:04:38:22:05:**
> > > > 
> > > > 
> > > > Thanks in advance i tried googling it but i don't think i could think of
> > > > the right combination of search phrase.
> > > > 
> > > > NJ
> > > But the associated question do you really want to set the WEP encryption
> > > code in hex rather than in ASCII, which is another option.
> > 
> > He needs to be sure he matches the setting used on the AP.  It won't
> > work if he uses the wrong type in the applet.  That said, most APs don't
> > use ASCII passphrases (it was an older lucent thing), so I'd expect it
> > to be a hex key, most likely.
> > 
> > Dan
> Dan,
> You may be right but all of the wireless APs distributed by AT&T have
> ASCII WEP passwds that are annoyingly 10 rather then 13 ASCII
> characters.

Yikes; that's 40-bit WEP then, and ASCII passphrases are even less
secure than a good 40-bit WEP hex key because the range of values you
can enter with ASCII passphrases is much more limited.  Sort of
disturbing, but these things should be trivial to crack if you care.

Dan