On Thu, Sep 19, 2013 at 12:49 PM, Sivaram R wrote:
> Karkar,
>
>I am not getting your point.I am using django default user model,my
> requirement is,after the user successfully login,their is a page called
> update user profile,their i am showing first name,last name,email are in
> update mod
Karkar,
I am not getting your point.I am using django default user model,my
requirement is,after the user successfully login,their is a page called
update user profile,their i am showing first name,last name,email are in
update mode but password is showing the hashed value and not the origin
R u looking at the password from the admin?
Sivaram R wrote:
I have views.py to show the form instance and update the instance.
On edit the form data,all other field are showing the correct value,password
field is showing the entire hashed value from database and not the entered
password.
I
Django doesn't store the original password, that would be a huge security
hole. It only has the hashed password available.
On Wednesday, September 18, 2013 10:10:02 AM UTC-5, Sivaram R wrote:
>
> I have views.py to show the form instance and update the instance.
>
> On edit the form data,all othe
That is a bad idea. It leaves your users vulnerable to a server or
database or database backup compromise.
The design is that if your server/database doesn't know the password, it
can't give it up.
If you truly want to store passwords in the clear, you will have to
re-implement the authenticatio
5 matches
Mail list logo
