Last modified: 2012-02-08 17:32:07 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T36237, the corresponding Phabricator task for complete and up-to-date bug report information.
First Last Prev Next    This bug is not in your last search results.
Bug 34237 - user_token should automatically regenerate when NULL
user_token should automatically regenerate when NULL
Status: RESOLVED FIXED
Product: MediaWiki
Classification: Unclassified
User login and signup (Other open bugs)
unspecified
All All
: Normal normal (vote)
: ---
Assigned To: Nobody - You can work on this!
:
Depends on:
Blocks:
  Show dependency tree / graph
 
Reported: 2012-02-07 03:15 UTC by Daniel Friesen
Modified: 2012-02-08 17:32 UTC (History)
1 user (show)

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Description Daniel Friesen 2012-02-07 03:15:50 UTC 
Currently if a copy of your user table gets leaked out you have to regenerate the entire user_token column. I'm not even sure we have a user script to do that.

The User class code should be tweaked so that if a user_token is found to be NULL when a user is logging in a new one will be generated and the row will be updated.

This way instead of needing a maintenance script, all it will take to re-secure the database after a leak would be for the sysadmin to run `UPDATE user SET user_token = NULL;` and user tokens will be regenerated as needed.
Comment 1 Daniel Friesen 2012-02-07 08:12:58 UTC 
r110825
Note You need to log in before you can comment on or make changes to this bug.
First Last Prev Next    This bug is not in your last search results.

Navigation
Links