Closed
Bug 731218
Opened 13 years ago
Closed 12 years ago
investigate: use PASSWORD_HASHERS setting (not needed with BrowserID?)
Categories
(developer.mozilla.org Graveyard :: Wiki pages, defect, P2)
Tracking
(Not tracked)
RESOLVED
WONTFIX
People
(Reporter: groovecoder, Unassigned)
References
Details
(Whiteboard: u=developer c=infrastructure p=)
django 1.4 adds PASSWORD_HASHERS setting so we can refactor our monkey-patching. But if we're 100% on BrowserID by then, we may just WONTFIX this.
|
||
Updated•13 years ago
|
Whiteboard: u=developer c=infrastructure p= → u=developer c=infrastructure s=2012-06-05 p=
|
|
||
Updated•13 years ago
|
Priority: -- → P2
|
||
Updated•13 years ago
|
Whiteboard: u=developer c=infrastructure s=2012-06-05 p= → u=developer c=infrastructure p=
|
Assignee | |
Updated•13 years ago
|
Version: Kuma → unspecified
|
|
Assignee | |
Updated•13 years ago
|
Component: Website → Landing pages
|
||
Comment 1•12 years ago
|
||
100% BrowserID.
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → WONTFIX
|
||
Updated•5 years ago
|
Product: developer.mozilla.org → developer.mozilla.org Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•