Skip to main content
replaced http://security.stackexchange.com/ with https://security.stackexchange.com/
Source Link

If you ask this question on security.stackexchangesecurity.stackexchange, the answer will be definite - don't reveal password, ever. It's akin to the poor practice of clicking forgotten password and being emailed your plain-text passwordbeing emailed your plain-text password, rather than a set of instructions on resetting it. While a user may get frustrated with this UX (Why can't I just see my password right now? Why do I have to reset my password?), security best practices are more important.

Incidentally, any browser allows you to reveal your password due to the mutable nature of DOM (document object model, a in-browser representation of page html). I've used this many-a-time whenever Chrome has better memory than I (normally my "user story" is that I have to log in from another device, and don't remember the password). To test this, go to any login page that your browser stores credentials for, like office365 below:

before tampering

You may have to type in your username before the password asterisks appear, now inspect the password field (in most browsers it's done via right click -> inspect element). If you delete the type="password" attribute, the password field will default to a vanilla text input and you will see the field's value in cleartext. I'm not adding that screenshot though :)

If you ask this question on security.stackexchange, the answer will be definite - don't reveal password, ever. It's akin to the poor practice of clicking forgotten password and being emailed your plain-text password, rather than a set of instructions on resetting it. While a user may get frustrated with this UX (Why can't I just see my password right now? Why do I have to reset my password?), security best practices are more important.

Incidentally, any browser allows you to reveal your password due to the mutable nature of DOM (document object model, a in-browser representation of page html). I've used this many-a-time whenever Chrome has better memory than I (normally my "user story" is that I have to log in from another device, and don't remember the password). To test this, go to any login page that your browser stores credentials for, like office365 below:

before tampering

You may have to type in your username before the password asterisks appear, now inspect the password field (in most browsers it's done via right click -> inspect element). If you delete the type="password" attribute, the password field will default to a vanilla text input and you will see the field's value in cleartext. I'm not adding that screenshot though :)

If you ask this question on security.stackexchange, the answer will be definite - don't reveal password, ever. It's akin to the poor practice of clicking forgotten password and being emailed your plain-text password, rather than a set of instructions on resetting it. While a user may get frustrated with this UX (Why can't I just see my password right now? Why do I have to reset my password?), security best practices are more important.

Incidentally, any browser allows you to reveal your password due to the mutable nature of DOM (document object model, a in-browser representation of page html). I've used this many-a-time whenever Chrome has better memory than I (normally my "user story" is that I have to log in from another device, and don't remember the password). To test this, go to any login page that your browser stores credentials for, like office365 below:

before tampering

You may have to type in your username before the password asterisks appear, now inspect the password field (in most browsers it's done via right click -> inspect element). If you delete the type="password" attribute, the password field will default to a vanilla text input and you will see the field's value in cleartext. I'm not adding that screenshot though :)

Source Link
Oleg
  • 390
  • 1
  • 13

If you ask this question on security.stackexchange, the answer will be definite - don't reveal password, ever. It's akin to the poor practice of clicking forgotten password and being emailed your plain-text password, rather than a set of instructions on resetting it. While a user may get frustrated with this UX (Why can't I just see my password right now? Why do I have to reset my password?), security best practices are more important.

Incidentally, any browser allows you to reveal your password due to the mutable nature of DOM (document object model, a in-browser representation of page html). I've used this many-a-time whenever Chrome has better memory than I (normally my "user story" is that I have to log in from another device, and don't remember the password). To test this, go to any login page that your browser stores credentials for, like office365 below:

before tampering

You may have to type in your username before the password asterisks appear, now inspect the password field (in most browsers it's done via right click -> inspect element). If you delete the type="password" attribute, the password field will default to a vanilla text input and you will see the field's value in cleartext. I'm not adding that screenshot though :)