| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
| |
afranke.
|
| |
|
|
| |
commit didn't pick these up.
|
| | |
|
| |
|
|
|
|
|
| |
the db when required instead.
(Also fixes bug 58242 as a side effect)
r=myk, kiko
|
| |
|
|
|
| |
Patch by Brad Baetz <bbaetz@student.usyd.edu.au>
r= jake, justdave
|
| |
|
|
|
|
|
| |
not locked", fixed typo in lock tables command.
Patch by Myk Melez <myk@mozilla.org>
r= jake@acutex.net
|
|
|
in plaintext in the database. Passwords are no longer encrypted with MySQL's ENCRYPT() function (because it doesn't work on some installs), but with Perl's crypt() function. The crypt-related routines now properly deal with salts so that they work on systems that use methods other than UNIX crypt to crypt the passwords (such as MD5). Checksetup.pl will walk through your database and re-crypt everyone's passwords based on the plaintext password entry, then drop the plaintext password column. As a consequence of no longer having a plaintext password, it is no longer possible to email someone their password, so the login screen has been changed to request a password reset instead. The user is emailed a temporary identifying token, with a link back to Bugzilla. They click on the link or paste it into their browser and Bugzilla allows them to change their password.
Patch by Myk Melez <myk@mozilla.org>
r= justdave@syndicomm.com, jake@acutex.net
|
