From: Johannes Berg <johannes@sipsolutions.net>
To: Josh Lehan <krellan@krellan.com>
Cc: linux-wireless@vger.kernel.org
Subject: Re: Distinguishing wrong password from other failure to connect?
Date: Fri, 12 Nov 2010 08:51:05 -0800 [thread overview]
Message-ID: <1289580665.3736.2.camel@jlt3.sipsolutions.net> (raw)
In-Reply-To: <4CDCEBE9.8060905@krellan.com>
On Thu, 2010-11-11 at 23:25 -0800, Josh Lehan wrote:
> This seems to be a common problem, because on many distributions, I see
> NetworkManager constantly popping up the password entry box whenever an
> association fails, when the user already knows the password is correct
> (and in fact has entered it into the box already, as it's pre-filled in
> the box, albeit starred out).
It should only have that issue with WEP (which you shouldn't be using
anyway) and even then only when shared key auth is not available.
Otherwise, the supplicant should have enough info about the failure.
johannes
next prev parent reply other threads:[~2010-11-12 16:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-12 7:25 Distinguishing wrong password from other failure to connect? Josh Lehan
2010-11-12 16:51 ` Johannes Berg [this message]
2010-11-12 17:21 ` Paul Stewart
2010-11-14 2:36 ` Josh Lehan
2010-11-13 10:34 ` Jouni Malinen
2010-11-14 2:47 ` Josh Lehan
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1289580665.3736.2.camel@jlt3.sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=krellan@krellan.com \
--cc=linux-wireless@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).