Bug 111519 - password requirements while registering are too strict
password requirements while registering are too strict
Product: Red Hat Enterprise Linux 3
Classification: Red Hat
Component: up2date (Show other bugs)
athlon Linux
medium Severity medium
: ---
: ---
Assigned To: Bret McMillan
Fanny Augustin
Depends On:
Blocks: 120092
  Show dependency treegraph
Reported: 2003-12-04 15:13 EST by Josh Kelley
Modified: 2007-11-30 17:06 EST (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2007-10-19 15:32:25 EDT
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 Josh Kelley 2003-12-04 15:13:28 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.5)

Description of problem:
While trying to register a new system under an existing account using
up2date, I enter my username and password and get the following error:

Error message:
   password contains character `"'
Error Class Code: 15
Error Class Info: The username contains invalid characters.

Three problems:
1. Up2date should accept a wider range of characters in passwords to
permit more secure passwords.
2. Up2date should at least accept the same range of characters for
passwords that the RHN and RedHat web sites accept when setting passwords.
3. The Error Class Info is not correct; the problem is with the
password, not the username.

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

How reproducible:

Steps to Reproduce:
1. From the RHN web site, change the account password to include a ".
2. Run up2date to register a new system with RHN.
3. Enter the username and password for the account from step 1.


Actual Results:  Error message:
   password contains character `"'

Expected Results:  Successful registration.

Additional info:
Comment 1 RHEL Product and Program Management 2007-10-19 15:32:25 EDT
This bug is filed against RHEL 3, which is in maintenance phase.
During the maintenance phase, only security errata and select mission
critical bug fixes will be released for enterprise products. Since
this bug does not meet that criteria, it is now being closed.
For more information of the RHEL errata support policy, please visit:
If you feel this bug is indeed mission critical, please contact your
support representative. You may be asked to provide detailed
information on how this bug is affecting you.

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