I'm not sure why you think that would be a better way? Assuming you are already using TLS correctly (2048 bit keys, TLS v1.2, proper cipher suites, forward secrecy, etc. etc.) a simple way to achieve much higher security is to support two factor authentication.
There are a number of systems for doing what you at trying to achieve (SRP is mentioned in another thread) but all of those are attempts to deal with significant man-in-the-middle concerns, not general we security. If you actually do have to deal with significant MITM concerns you really need a security expert on your team. In actuality, if you are doing things right, the biggest security issues are exploits on the client side (viruses, phishing, key-loggers) and incursions into your infrastructure. Rob. On Saturday, January 14, 2017 at 1:24:24 PM UTC-5, Chris Priest wrote: > > The way django's authentication system works is that when you register, > you send the password to the server, then the server runs that password > through some hashing algorithms, then the resulting hash is stored in the > database. When the user logs in, the password again is sent to the server, > and the hash is calculated and then compared to the hash that was > calculated when they registered. > > This results in the plain text password not being stored in the database, > but the password is still being sent back to the server. A better way would > be for the hash to be calculated on the front end, in javascript, and then > sent back to be stored in the database. This way, the user *knows for sure* > that the password isn't being saved in plain text because the server > doesn't even know the plain text password. > > Has anyone ever tried building an authentication system that worked this > way? If someone built such a thing, could it get included in django contrib? > -- 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 django-developers+unsubscr...@googlegroups.com. To post to this group, send email to django-developers@googlegroups.com. 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/ccf786f9-ade1-49c1-942b-0219cd441086%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
