Hi there, On Wednesday, November 7, 2018 at 10:22:06 PM UTC+1, Alex Toussaint wrote: > > I've been able, with a simple Python script, from having read-only access > to my Django webserver to a full read-write by crafting a reset token. >
To be honest that script is weird at best; if you have access to the password hash, you will most likely also have access to the last_login -- so why bruteforce it at all? And yes it is absolutely expected to be able to generate password reset tokens if you know the SECRET_KEY (!!!), the password hash, last_login & id. Isn't it one of the main goals of hashing passwords ? Protecting from > attackers having read only access to the database ? > No, the main goal of hashing passwords is not leaking the __original__ password. It also protects against attackers with read only access to the database as long as the hash functions are sufficiently good (you can always try to bruteforce the password). Cheers, Florian -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/64cef8de-b463-4f98-b439-a98498bb9133%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
