Hello all,
I'm currently working on an implementation of the server-side of an
already-defined protocol. So, no, I can't do things differently. :)
The protocol performs authentication by passing a token which is
"md5(md5(password) + timestamp)" and the timestamp. I then need to
calculate the same on the server.
However, I don't have direct access to either 'password' or
'md5(password)', so I can't do this.
There are a couple of ways I can think of to deal with this:
* Store the MD5 of the password in a separate location. This is
nasty because it means I need to be aware of whenever the
password is changed.
* Force Django to use MD5 to store passwords. This is nasty
because it means I have to use MD5 for passwords. However, I'm
already being forced to use MD5 elsewhere, so I'd be happy to do
this if it's possible.
I'd be interested to hear other ideas about how I could get around this,
and suggestions as to how to implement the above two.
Thanks,
Dan
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Django users" group.
To post to this group, send email to django-users@googlegroups.com
To unsubscribe from this group, send email to
django-users+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/django-users?hl=en
-~----------~----~----~----~------~----~------~--~---
