On Wed, Mar 22, 2006 at 03:34:07PM -0500, Robert Love wrote:
So I have two questions: what are the EAP versions of the 2nd
authentications? E.g., what is EAP-TTLS/EAP-MSCHAPv2 and how does it
differ from EAP-TTLS/MSCHAPv2 ?
EAP-TTLS allows phase 2 (tunneled) authentication to use both EAP
On Fri, 2006-03-24 at 07:23 -0800, Jouni Malinen wrote:
I've been working with more documentation for wpa_supplicant
configuration and one part of this is a configuration wizard that can
be used to generate example configurations. It is not yet complete and
is likely to miss something.
On Wed, 2006-03-22 at 14:50 -0500, Robert Love wrote:
Jan and Dennis, I would love to hear if it works for you and, if not,
what goes wrong.
I'd like to report that it works for me! Thanks, Robert (and others too,
of course!). The only problem I have that network interface switching
doesn't
On Thu, 2006-03-23 at 11:48 +0100, Dennis Kaarsemaker wrote:
How about:
_
Key type:| Wep 40 \/ |
|-|
| Wep 64 |
| WPA |
Dennis Kaarsemaker wrote:
...and of course Murphy loves me and decided that somehow madwifi scuks
even harder than I thought - with the neccessary patches applied to NM
and the madwifi Driver all worked fine a few days ago but today it
decided not to do WPA anymore. So I won't be able to test
On Thu, 2006-03-23 at 10:04 -0500, Pat Suwalski wrote:
Finally, if you've gotten this far, there is a patch I'm planning to
write that will automatically detect the WEP type, there is no need for
a drop-down box. Hex will be hex, 26 characters/nibbles long. The
password mode for that does
On Thu, 2006-03-23 at 10:15 -0500, Pat Suwalski wrote:
Robert Love wrote:
This won't fly.
As just one example, my passphrase at home is a legitimate hex key (I
am, yes, an idiot). Differentiating between ASCII and passphrase is
even harder. We need to ask.
I've seen this in an
On Thu, 2006-03-23 at 10:15 -0500, Pat Suwalski wrote:
Robert Love wrote:
This won't fly.
As just one example, my passphrase at home is a legitimate hex key (I
am, yes, an idiot). Differentiating between ASCII and passphrase is
even harder. We need to ask.
I've seen this in an
On Thu, 2006-03-23 at 10:22 -0500, Dan Williams wrote:
Passphrases can be any length, up to 64 characters. That includes
exactly 26 characters, and since the hex key character space is a subset
of the passphrase character space, there's absolutely no way to
differentiate between the two
Robert Love wrote:
Basically:
WEP key: 26 characters, [A-F]|[a-f]|[0-9]
String: 26 characters, no restrictions.
I am saying, my passphrase is a legitimate hex key.
It cannot work beautifully if ASCII and Hex keys are also valid
passphrases.
I don't see how -- to the best
On Thu, 2006-03-23 at 10:43 -0500, Pat Suwalski wrote:
I don't see how -- to the best of my knowledge, the ascii keys are not
allowed to be 26 characters long, and the hex keys must be 26 characters
long...
Right, but passphrases can be either of those things.
Robert Love
Robert Love wrote:
I think many users these days, and most users going forward, use
passphrases, so the best bet we can have is default to passphrase as
the key type and expect our users to change it if needed. Otherwise, as
Dan wrote, we are just asking for confusion.
Hm. Well, then
On Thu, 2006-03-23 at 10:51 -0500, Pat Suwalski wrote:
Hm. Well, then something that would alleviate the annoyance is if the
text box didn't get cleared when the mode is changed. I always end up
pasting in or typing in the key and then selecting the method, only to
lose about 2 minutes of
Hi, guys.
I checked a first-pass at Dynamic WEP into CVS, on both HEAD and the 0.6
branch (since it was not overly complex).
Jan and Dennis, I would love to hear if it works for you and, if not,
what goes wrong.
Thanks!
Robert Love
___
On Wed, 2006-03-22 at 14:50 -0500, Robert Love wrote:
I checked a first-pass at Dynamic WEP into CVS, on both HEAD and the 0.6
branch (since it was not overly complex).
Jan and Dennis, I would love to hear if it works for you and, if not,
what goes wrong.
If not obvious: Select Dynamic WEP
On wo, 2006-03-22 at 14:54 -0500, Robert Love wrote:
If not obvious: Select Dynamic WEP as the Key type in the WPA
Enterprise configuration.
Another question is, if NM detects your Dynamic WEP-based AP, does it
think it is doing WPA Enterprise? It should.
Robert, you rock!
I'll test in
On Wed, 2006-03-22 at 21:14 +0100, Jan Mynarik wrote:
Another question is, if NM detects your Dynamic WEP-based AP, does it
think it is doing WPA Enterprise? It should.
No, when I select this network from nm-applet's list, n-m tries to
connect and then opens dialog asking for WEP
Hello.
On Wed, 2006-03-22 at 15:08, Robert Love wrote:
to wpa_supplicant if the user selects a specific option. But I need to
better understand the problem. What is PAP ? What other second-stage
authentications are there? Are they only valid with certain ciphers?
From the
On wo, 2006-03-22 at 15:14 -0500, Robert Love wrote:
Hrm. That is a problem. Kind of sucks if there is no way for the AP
to advertise that it does half-WPA/half-WEP. I presumed it would
advertise the WPA-EAP stuff, but then non-WPA cards might not grok
that.
There is no such way indeed.
On Wed, 2006-03-22 at 15:14 -0500, Robert Love wrote:
On Wed, 2006-03-22 at 21:14 +0100, Jan Mynarik wrote:
Another question is, if NM detects your Dynamic WEP-based AP, does it
think it is doing WPA Enterprise? It should.
No, when I select this network from nm-applet's list, n-m
20 matches
Mail list logo
