user login should be implemented
oguzy opened this issue · comments
The uploaded data is saved according to the user_id, better to define a user and a login screen
Good idea. Just don't implement unsalted sha1 hashing when you store the password ;)
You may want to ask for user name (anithing), user id (valid email) and password. store only hash of user id and pass.
Nicolas
On 9 Jun, 2012, at 18:38, Oğuz Yarımtepereply@reply.github.com wrote:
The uploaded data is saved according to the user_id, better to define a user and a login screen
Reply to this email directly or view it on GitHub:
https://github.com/oguzy/openwitness/issues/4
Passwords are salted and user email is kept as it hash value. Users should be created manually, for now. A script is defined for this issue.
Wonderful! Thanks.
On 11 Jun, 2012, at 1:15, Oğuz Yarımtepereply@reply.github.com wrote:
Passwords are salted and user email is kept as it hash value. Users should be created manually, for now. A script is defined for this issue.
Reply to this email directly or view it on GitHub:
https://github.com/oguzy/openwitness/issues/4#issuecomment-6229992
http://blog.mozilla.org/webdev/2012/06/08/lets-talk-about-password-storage/
-->
django-sha2. : https://github.com/fwenzel/django-sha2
On Jun 11, 2012, at 1:15 AM, Oğuz Yarımtepe wrote:
Passwords are salted and user email is kept as it hash value. Users should be created manually, for now. A script is defined for this issue.
Reply to this email directly or view it on GitHub:
https://github.com/oguzy/openwitness/issues/4#issuecomment-6229992