Closed
Bug 341088
Opened 19 years ago
Closed 19 years ago
Use of uninitialized value in crypt at Bugzilla/Util.pm line 339.
Categories
(Bugzilla :: Installation & Upgrading, defect)
Tracking
()
RESOLVED
WONTFIX
People
(Reporter: mkgnu, Unassigned)
Details
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.10) Gecko/20060505 Firefox/1.0.4 (Debian package 1.0.4-2sarge7)
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.10) Gecko/20060505 Firefox/1.0.4 (Debian package 1.0.4-2sarge7)
I attempted to upgrade a Bugzilla 2.10 instance to 2.20.2. While running checksetup.pl I observed the following:
Updating column cryptpassword in table profiles ...
Old: varchar(64)
New: varchar(128)
Your current installation of Bugzilla stores passwords in plaintext
in the database and uses mysql's encrypt function instead of Perl's
crypt function to crypt passwords. Passwords are now going to be
re-crypted with the Perl function, and plaintext passwords will be
deleted from the database. This could take a while if your
installation has many users.
Fixing password #1... Use of uninitialized value in crypt at
Bugzilla/Util.pm line 339.
Use of uninitialized value in crypt at Bugzilla/Util.pm line 339.
Use of uninitialized value in crypt at Bugzilla/Util.pm line 339.
Use of uninitialized value in crypt at Bugzilla/Util.pm line 339.
Use of uninitialized value in crypt at Bugzilla/Util.pm line 339.
Use of uninitialized value in crypt at Bugzilla/Util.pm line 339.
Use of uninitialized value in crypt at Bugzilla/Util.pm line 339.
Use of uninitialized value in crypt at Bugzilla/Util.pm line 339.
Use of uninitialized value in crypt at Bugzilla/Util.pm line 339.
Use of uninitialized value in crypt at Bugzilla/Util.pm line 339.
Use of uninitialized value in crypt at Bugzilla/Util.pm line 339.
Use of uninitialized value in crypt at Bugzilla/Util.pm line 339.
Use of uninitialized value in crypt at Bugzilla/Util.pm line 339.
Use of uninitialized value in crypt at Bugzilla/Util.pm line 339.
Use of uninitialized value in crypt at Bugzilla/Util.pm line 339.
Use of uninitialized value in crypt at Bugzilla/Util.pm line 339.
Use of uninitialized value in crypt at Bugzilla/Util.pm line 339.
Use of uninitialized value in crypt at Bugzilla/Util.pm line 339.
Use of uninitialized value in crypt at Bugzilla/Util.pm line 339.
Use of uninitialized value in crypt at Bugzilla/Util.pm line 339.
Use of uninitialized value in crypt at Bugzilla/Util.pm line 339.
Use of uninitialized value in crypt at Bugzilla/Util.pm line 339.
Use of uninitialized value in crypt at Bugzilla/Util.pm line 339.
Use of uninitialized value in crypt at Bugzilla/Util.pm line 339.
Use of uninitialized value in crypt at Bugzilla/Util.pm line 339.
Use of uninitialized value in crypt at Bugzilla/Util.pm line 339.
Use of uninitialized value in crypt at Bugzilla/Util.pm line 339.
28... Done.
Deleting unused column password from table profiles ...
Reproducible: Didn't try
Actual Results:
I'm still able to login after the upgrade.
Expected Results:
I suppose something that does not give this warning.
![]() |
||
Comment 1•19 years ago
|
||
mkanat, known bug?
Comment 2•19 years ago
|
||
Yes, I've seen this problem. It means that something was wrong with your old database, and certain users had NULL for a password, I think. It only happens on upgrades from extremely old versions of Bugzilla, and it has no effect that I can see.
Thus I'm going to WONTFIX it.
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago
Resolution: --- → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•