Re: Clarification of key terminaology.
the passphrase generates an ascii key that then is used to authenticate. the passphrase generally can contain spaces, while key usually don't. 2008/1/22, Aaron Konstam [EMAIL PROTECTED]: I am still unclear as to what is the difference between ASCII key and a passphrase? Can the latter have blanks in it or what? -- -- === Depart in pieces, i.e., split. === Aaron Konstam telephone: (210) 656-0355 e-mail: [EMAIL PROTECTED] ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list -- dott. ing. beso ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Clarification of key terminaology.
I am still unclear as to what is the difference between ASCII key and a passphrase? Can the latter have blanks in it or what? -- -- === Depart in pieces, i.e., split. === Aaron Konstam telephone: (210) 656-0355 e-mail: [EMAIL PROTECTED] ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Clarification of key terminaology.
On Tue, 22 Jan 2008, Ryan Novosielski wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 ASCII and hex keys go together in that one is just the opposite representation of the other. I believe 40-bit is 5 chars long in ASCII and 128-bit is 13 chars, but I could be messing that up. I have no idea what the passphrase one is, but it's not something I can use. What AP do you have? Every consumer AP sold in the last 5 years uses WEP passphrases, not ASCII keys. Chances are that you have encountered passphrases before, but since the WEP key situation is so confusing, you may not know it. Dan Aaron Konstam wrote: I am still unclear as to what is the difference between ASCII key and a passphrase? Can the latter have blanks in it or what? -- -- === Depart in pieces, i.e., split. === Aaron Konstam telephone: (210) 656-0355 e-mail: [EMAIL PROTECTED] ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list - -- _ _ _ _ ___ _ _ _ |Y#| | | |\/| | \ |\ | | |Ryan Novosielski - Systems Programmer II |$| |__| | | |__/ | \| _| |[EMAIL PROTECTED] - 973/972.0922 (2-0922) \__/ Univ. of Med. and Dent.|IST/AST - NJMS Medical Science Bldg - C630 -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFHlgxrmb+gadEcsb4RAktHAJ9rDs6ew/ixiNHlWOu5A9ZTq+GkDACgpwFL 7oJrt/Sj+kqfdjazpOLgsnE= =844m -END PGP SIGNATURE- ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Clarification of key terminaology.
On Tue, 22 Jan 2008, Aaron Konstam wrote: I am still unclear as to what is the difference between ASCII key and a passphrase? Can the latter have blanks in it or what? Both can. ASCII keys/passwords must be either 5 or 13 characters in length (depending on whether you're using 40/64 bit WEP or 104/128 bit WEP). WEP Passphrases can be any length up to 64 characters I believe. The difference is in how the input (either ASCII key or WEP passphrase) gets turned into the actual key that is delivered to the driver. For the ASCII key, the raw ASCII values of what you type directly compose the key values. For WEP passphrases, what you type is repeated over and over until 64 bytes have been filled, then it is hashed with MD5, and the resulting hash is the WEP key. I can try to find some stuff online about the actual key hashing process if you like. Cheers, Dan -- -- === Depart in pieces, i.e., split. === Aaron Konstam telephone: (210) 656-0355 e-mail: [EMAIL PROTECTED] ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Clarification of key terminaology.
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Dan Williams wrote: On Tue, 22 Jan 2008, Ryan Novosielski wrote: ASCII and hex keys go together in that one is just the opposite representation of the other. I believe 40-bit is 5 chars long in ASCII and 128-bit is 13 chars, but I could be messing that up. I have no idea what the passphrase one is, but it's not something I can use. What AP do you have? Every consumer AP sold in the last 5 years uses WEP passphrases, not ASCII keys. Chances are that you have encountered passphrases before, but since the WEP key situation is so confusing, you may not know it. I don't use an AP -- I use a Lucent WaveLAN Gold card in a Debian 3 or 4 (I forget which and I'm in a fuss with Verizon at the moment and have no DSL). Thinking back on it, it's quite possible that I just don't know how to have Linux generate a passphrase. I don't think I've seen the option in iwconfig, however. - -- _ _ _ _ ___ _ _ _ |Y#| | | |\/| | \ |\ | | |Ryan Novosielski - Systems Programmer II |$| |__| | | |__/ | \| _| |[EMAIL PROTECTED] - 973/972.0922 (2-0922) \__/ Univ. of Med. and Dent.|IST/AST - NJMS Medical Science Bldg - C630 -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFHlietmb+gadEcsb4RAil3AKDJ2GhbciEj/tpTKJk+Qvdl7xBdVwCg4NbI rZock7Qg6SZgZltyRtvBIzk= =3o+C -END PGP SIGNATURE- begin:vcard fn:Ryan Novosielski n:Novosielski;Ryan org:UMDNJ;IST/AST adr;dom:MSB C630;;185 South Orange Avenue;Newark;NJ;07103 email;internet:[EMAIL PROTECTED] title:Systems Programmer III tel;work:(973) 972-0922 tel;fax:(973) 972-7412 tel;pager:(866) 20-UMDNJ x-mozilla-html:FALSE version:2.1 end:vcard ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
