4 ms·
Err, I think that's a bit of a strawman fallacy. If you leave your computer unlocked in a public area, that's asking for trouble - which is the example I was r
by victorhooi 13y ago
Err, I think that's a bit of a strawman fallacy.
If you leave your computer unlocked in a public area, that's asking for trouble - which is the example I was referring to.
However, in your example, you cited giving your machine to a friend to debug code - in that case, you either trust your friend, or you don't.
If you don't trust your friend, why are you giving them your machine then.
It's like asking your friend to collect your letterbox mail - do you trust them enough to not open and read your mail? If you don't, then why are you entrusting them to collect your mail?
- interpol_p 13y agoHave you ever glanced slightly harder than you should when your friend enters their four digit pin code on their phone? I have. And it's not out of malicious intent. There are levels of trust. It's not binary, and it's not as simple as you make it out to be. Because Chrome presents your passwords in an easily accessible list from the settings screen, it lowers the barrier to access and increases the opportunity for passwords to be read. Maybe my friend wants to read my passwords out of idle curiosity and they won't do anything malicious with them. I don't know, and I don't want to find out. It is not at all like asking your friend to collect your mail. First, you can easily see if your mail has been opened. And for your friend to "cover up" opening your mail they would have to have some serious intent to breach your trust. This is not so with the password screen in Chrome. I'm surprised that you can't see how making the passwords to all your websites easily accessible and readable in a convenient list is a bad thing. Adding a simple hurdle to access is all that's needed to prevent the majority of casual peeking at peoples' passwords. Safari does this, there is no technical reason Chrome can't.