Changes between Version 2 and Version 3 of CookBookPasswordGreasemonkeyUserScript


Ignore:
Timestamp:
04/30/06 11:13:30 (9 years ago)
Author:
akaihola
Comment:

Added explanation, remote install link and a note.

Legend:

Unmodified
Added
Removed
Modified
  • CookBookPasswordGreasemonkeyUserScript

    v2 v3  
    11Django admin expects users' passwords to be entered as SHA-1 hashes in the format {{{[algo]$[salt]$[hexdigest]}}}. Here is a tool which automates calculating the hashes on the client side.
     2
     3What it does as of version 1.0 is:
     4 * searches each opened page for an {{{<input>}}} with {{{id="id_password"}}}, {{{class="vTextField required"}}}, {{{name="password}}}, {{{size="30"}}} and {{{maxlength="128"}}}, which is how the password field is defined in Django admin
     5 * when the password field loses focus, replaces its contents with a SHA-1 salted hash as Django expects
     6 * does not modify field contents if it's already a hash
    27
    38You need to
    49 * use the Firefox browser
    510 * install the [http://greasemonkey.mozdev.org/ Greasemonkey] extension
    6  * install the [wiki:CookBookDjangoPasswordHasherUserJs djangopasswordhasher.user.js] user script
     11 * install the [http://svn.ambitone.com/ambidjangolib/js/djangopasswordhasher.user.js djangopasswordhasher.user.js] user script
    712
    813Pros:
     
    1217Cons:
    1318 * needs the extension on the browser
     19 * doesn't use a real password field -- password entry is visible
     20
     21---
     22
     23''Note:'' Don't try to install the script using the attachments below. Use the remote link above instead. Admins should remove the attachments.
Back to Top