Age | Commit message (Collapse) | Author | Files | Lines |
|
patch by dkl. r=kiko
|
|
Patch by Nick Hibma <n_hibma@qubesoft.com>
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
|
|
userregexp for groupsets.
Patch by Joe Robins <jmrobins@tgix.com>
r= jake@acutex.net
|
|
r= justdave@syndicomm.com
|
|
|
|
based on patch submitted by baulig@suse.de (Martin Baulig).
|
|
get sent to an account. Original patch by al_raetz@yahoo.com and lots of additional hacking by me; r=donm@bluemartini.com
|
|
patch by jmrobin@tgix.com
|
|
by jmrobins@tgix.com (Joe Robins). LDAP sections haven't been
tested yet, but the code is arranged such that it shouldn't disturb
existing user authentication system.
|
|
john.beranek@pace.co.uk (John Beranek)
|
|
accident.
|
|
|
|
|
|
submitted by JRobertson@medevolve.com (Jon Robertson)
|
|
|
|
Patches and work contributed by dave@intrec.com (Dave Miller).
Some cleanup work needs to be done with regards to permissions and bit-twiddling
see other bugs that are dependent on 25010 for details.
|
|
|
|
"editbugs" and "canconfirm". People without these states are now much
more limited in what they can do.
For backwards compatability, by default all users will have the
editbugs and canconfirm bits on them. Installing this changes as is
should only have one major visible effect -- an UNCONFIRMED state
will appear in the query page. But no bugs will become in that state,
until you tweak some of the new voting-related parameters you'll find
when editing products.
|
|
|
|
|
|
both was causing corruption on about 1 in 40 passwords.)
|
|
me. Added a footer to every page. Add some options to do things like
display checkboxes instead of scrolling lists, and a new formatting
for email diffs, and show list items capitalized instead of all upper
case.
|
|
|
|
ability to edit components, products, and versions. Yay!
|