thank you guys!
Miguel
Sent from Madrid, Spain
On Wed, Apr 29, 2009 at 2:22 PM, Ned Batchelder wrote:
>
> If you want to login as a user, don't bother with their password (which
> can't be decoded anyway). Build another authorization mechanism into
> your app so that you can log in as them with
If you want to login as a user, don't bother with their password (which
can't be decoded anyway). Build another authorization mechanism into
your app so that you can log in as them without a password. For
example, you can accept a user name with a password of (superuser name,
superuser passw
On Wednesday 29 April 2009 17:17:42 Miguel wrote:
> is there any way to decode the passwords that django keeps the the
> auth_user table?
afaik it is one way only
--
regards
kg
http://lawgon.livejournal.com
--~--~-~--~~~---~--~~
You received this message because
On Wed, Apr 29, 2009 at 7:47 AM, Miguel wrote:
> Hello,
>
> is there any way to decode the passwords that django keeps the the
> auth_user table? It would be really interesting to see if there is any
> problems in the users part of the web when new information and tasks are
> added via admin web.
On 29 Apr 2009, at 13:47 , Miguel wrote:
> Hello,
>
> is there any way to decode the passwords that django keeps the the
> auth_user
> table?
No. The passwords are stored salted hashes
(http://en.wikipedia.org/wiki/Salted_hash
), you can try brute-forcing them if you have *a lot* of time (and
Hello,
is there any way to decode the passwords that django keeps the the auth_user
table? It would be really interesting to see if there is any problems in the
users part of the web when new information and tasks are added via admin
web.
regards,
Miguel
Sent from Madrid, Spain
--~--~
6 matches
Mail list logo
