Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 181755 - NM hex wep key entry allows non-hex characters
NM hex wep key entry allows non-hex characters
Product: Fedora
Classification: Fedora
Component: NetworkManager (Show other bugs)
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Christopher Aillon
Depends On:
  Show dependency treegraph
Reported: 2006-02-16 04:03 EST by Bernard Johnson
Modified: 2007-11-30 17:11 EST (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2006-03-01 00:26:28 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Bernard Johnson 2006-02-16 04:03:58 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv: Gecko/20060210 Fedora/ Firefox/

Description of problem:
When attempting to a wep protected wireless network, the NM authentication dialog is presented for entry of the hex wep keys / ascii wep keys / wep passphrase.  When you select hex wep keys, the entry field for the key will accept non-hex values.

I can see this being a reasonable behavior if switching between hex/ascii/passphrase saved the value in the field, but this is not the case.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. Attempt to connect to wep network using NM
2. Wait for authentication dialog, choose hex wep key
3. Enter non-hex values

Actual Results:  Non-hex values were accepted as valid input for a hex only field.

Expected Results:  Field should have been filtered to 0-F.

Additional info:
Comment 1 Christopher Aillon 2006-03-01 00:26:28 EST
thanks.  filed upstream at http://bugzilla.gnome.org/show_bug.cgi?id=332951

Note You need to log in before you can comment on or make changes to this bug.