3 ms·
This probably is a mistake, far from harmless, but wouldn't it be better to point it out to the Chrome team and try to get it fixed. Have you logged a bug? htt
by grey-area 13y ago
This probably is a mistake, far from harmless, but wouldn't it be better to point it out to the Chrome team and try to get it fixed. Have you logged a bug?
https://code.google.com/p/chromium/ https://code.google.com/p/chromium/ or Tools > Report an issue...
- stephenr 13y agoA mistake..? So they accidentally wrote code to copy your credentials and create a new keychain item which Chrome has permanent access to?
- masklinn 13y agoIndeed, that doesn't point to a mistake when the right thing is 1. get the result from the query; 2. do nothing else because if the user choose "always allow" the OS itself will give Chrome permanent access.
- grey-area 13y agoThey're importing Safari data, so I'd expect them to copy the credentials to a new item to avoid conflicting with Safari managing that data, and creating a new keychain item with permanent access would be the correct response for 'Always Allow', so isn't it possible that's a mistake that they don't correctly respond to the Allow button? I agree storing the credentials outside keychain is not desirable, but again probably that has to do with cross-platform requirements rather than malice on the part of Google. Have you reported the bug and asked the Chrome team about it? In contrast to adwords defaulting to automatic payments and auto-bidding, or tracking users across the web universally over all the google services, or pushing people to use G+ everywhere, this wouldn't really benefit Google would it? I'm sure Google do lots of evil things, but I can't see any upside to them in this, and lots of downside.
- stephenr 13y agoDid you not read what I said? I never imported any bookmarks. I just opened Chrome, typed "twitter.com" and hit enter. It prompted for access to the single keychain entry for twitter.com and then created it's own copy after I hit "allow". No, it does not make any sense to create a copy, even if I was importing from Safari. If it's going to use the system keychain, it should use it in a sensible manner.
- aboustayyef 13y agoI noticed this a while ago. Google is being "evil" here in the sense that it doesn't want to use Apple's security tools (keychain access) and wants to use its own authentication methods. The correct (apple-canon) behavior is to ask for the password every time a user wants to access her keychain (until the end of the session). This doesn't suit google which has its own security paradigm of sign-in-once-access-until-signout. This is why it creates a copy of your passwords to do whatever it pleases with..
- aidos 13y agoI'm not so sure. You have to deliberately write that code.