Chrome's insane password security strategy

Re:Chrome's insane password security strategy by Shooti on Wednesday August 07, 2013 @09:11AM (#6172541)

"Inspect element" and then changing the "password" input type takes seconds/minutes.

[ Parent | on HN ]

Re:Chrome's insane password security strategy by interpol_p on Wednesday August 07, 2013 @09:17AM (#6172573)

Here are the issues with your method.

- It's not as fast or inconspicuous as navigating to chrome://settings/passwords

- It does not present all passwords in a single list with the ability to show the one I'm interested in

- I would have to go to each site, allow Chrome to auto-fill, and then inspect the DOM and change the input type for each password I'm interested in. Far slower.

- It feels far more malicious to do what you suggest. Feeling is important. If I feel like I'm doing something bad, I'm less likely to do it. If I feel like I'm innocently navigating the Chrome settings page then I'm more likely to take a peek at your passwords.

- Far fewer people will be comfortable or familiar, or capable of using the DOM modification method. If a novice practices they are likely to get good at it. But that goes back to malicious intent.

[ Parent | on HN ]

Re:Chrome's insane password security strategy by epicgear on Wednesday August 07, 2013 @12:01PM (#6173668)

i'm surprised that you even answered him ...

[ Parent | on HN ]