Op Wo, 2009-04-08 om 12:42 +1200 skryf Amos Jeffries: > > Op Di, 2009-03-31 om 00:49 +0100 skryf Flávio Martins:
... > > I've had an idea surrounding this and the other requirements posted here. > > One other approach that would possibly provide long-term flexibility to > pootle admin is to support multiple password security mechanisms. Adding a > type field to the DB paired with the stored passwd which determines what > hash/encrypt the auth stores things as. The auth mechanism would check the > existing storage type and either use it or do the submitted update > algorithm. > > Pros: > * allows pootle to support more than one security hash > * allows admin to select the security method they prefer. > * allows seamless migration between security methods. > * Pootle 1.2 can be imported as MD5 hash type in one go and the old file > dropped. Hallo Amos I think what you describe is mostly already possible with the way we use Django's authentication. In the current development version you will see in the file settings.py that we can optionally enable LDAP authentication, and actually specify a list of back-ends in the order that we prefer them to be used. I am just not sure if this can be used to perform migration in itself. Is there a way that somebody can think of? Friedel -- Recently on my blog: http://translate.org.za/blogs/friedel/en/content/monolingual-translation-formats-considered-harmful ------------------------------------------------------------------------------ This SF.net email is sponsored by: High Quality Requirements in a Collaborative Environment. Download a free trial of Rational Requirements Composer Now! http://p.sf.net/sfu/www-ibm-com _______________________________________________ Translate-pootle mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/translate-pootle
