On Wed, Jan 28, 2009 at 3:17 AM, Florent Aide <[email protected]> wrote: > > On Wed, Jan 28, 2009 at 5:37 AM, Jorge Vargas <[email protected]> wrote: >> >> Hello guys, >> >> today while upgrading an old project (1.9.7) to a more current version >> (2.0b4) I found a very interesting case. >> >> I used a custom script to create users which generated a very >> interesting result, here is a copy of the script. >> >> http://paste.chrisarndt.de/paste/5942bb29dab74c309a766638218f8f54 > > this script does not load the tg config... how could the tg model find > the auth encryption algo?
to be clear, that's my point why will that won't work? why will I need to load tg in order to use a console script? can't we just inline that in the model where it should be? Just as Gustavo said simply add the 3 lines to the model with the sha1 and md5 commented out and the salted_sha1 un-commented. That will let everyone default to the most secure algorith, yet still allow you to go back to the less-secure ones in case you need to (for example old already hashed passwords) --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "TurboGears Trunk" 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/turbogears-trunk?hl=en -~----------~----~----~----~------~----~------~--~---
