#6028: add compatibility with glibc2 MD5-based crypt passwords
---------------------------------------+------------------------------------
   Reporter:  akaihola                 |                Owner:  nobody      
     Status:  new                      |            Component:  Contrib apps
    Version:  SVN                      |           Resolution:              
   Keywords:  auth password crypt mp5  |                Stage:  Unreviewed  
  Has_patch:  1                        |           Needs_docs:  0           
Needs_tests:  0                        |   Needs_better_patch:  0           
---------------------------------------+------------------------------------
Changes (by akaihola):

  * needs_better_patch:  => 0
  * has_patch:  0 => 1
  * needs_tests:  => 0
  * needs_docs:  => 0

Comment:

 The above three alternate patches offer three different conventions for
 specifying MD5 crypt passwords.

 [attachment:md5-crypt.diff The first one] doesn't add a new algorithm
 name. It detects and correctly parses MD5 crypt passwords when the salt
 part of the password string starts with "{{{$1}}}".

 [attachment:md5-crypt-as-algo-name.diff The second one] adds
 "{{{md5-crypt}}}" as a new algorithm name, and MD5 crypt passwords must
 use it.

 [attachment:md5-crypt-as-algo-name-plus-autodetect The third one] adds the
 "{{{md5-crypt}}}" algorithm name, but also auto-detects MD5 crypt
 passwords when "{{{crypt}}}" is used as the algorithm name.

-- 
Ticket URL: <http://code.djangoproject.com/ticket/6028#comment:1>
Django Code <http://code.djangoproject.com/>
The web framework for perfectionists with deadlines
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to