The Computer Oracle

Google Chrome constantly asking for Keychain permission?

--------------------------------------------------
Rise to the top 3% as a developer or hire one of them at Toptal: https://topt.al/25cXVn
--------------------------------------------------

Music by Eric Matyas
https://www.soundimage.org
Track title: Quirky Dreamscape Looping

--

Chapters
00:00 Google Chrome Constantly Asking For Keychain Permission?
00:27 Answer 1 Score 1
00:43 Accepted Answer Score 6
01:49 Answer 3 Score 4
01:56 Answer 4 Score 18
02:30 Thank you

--

Full question
https://superuser.com/questions/171471/g...

--

Content licensed under CC BY-SA
https://meta.stackexchange.com/help/lice...

--

Tags
#osxsnowleopard #googlechrome #keychain

#avk47



ANSWER 1

Score 18


This is what worked for me. Apple Snow Leopard and Google Chrome 17.0.963.56.

  1. Quit Chrome
  2. Open Utilities: Keychain Access
  3. Search for Chrome
  4. Delete "Chrome Safe Storage"
  5. Start up Chrome. Note that Chrome Safe Storage is back in the list.
  6. Go to a site which requires a password stored in the Keychain. The Keychain dialog box will pop up and ask for your password. Type the password (like you normally do).



ACCEPTED ANSWER

Score 6


Google screwed up the application signing in their update procedure. I'm just randomly guess they switched the OS X binary over to something like what they were doing with the Windows version (a decompiling, then patching procedure, then recompiling) without considering the possibility of differing hashes.

Mac OS X 10.5 Leopard includes a new code signing security feature that helps verify the integrity of an application. Applications are signed by their creators before being distributed using their private key, and then can be verified on the customer’s machine using the company’s public key.

Mac OS X’s Keychain Services leverage this new code signing feature to verify the signature of each application before allowing access to the contents of the keychain. By verifying the signature, the Mac OS X keychain Services can detect when a potentially malicious change has been made to an application and thereby protect your sensitive data by denying the changed application access.

src: http://help.agile.ws/1Password3/invalid_code_signature.html

As for the fix? Not quite sure. I've just been hammering on Always Allow. I still get them sometimes but ever since I've started hammering, I've been getting less. Eventually, it'll go away if you keep doing that.

Hey, looking back at my guess, try reinstalling.




ANSWER 3

Score 4


Re-installing fixed the problem for me.




ANSWER 4

Score 1


In Keychain Access menu, try to run Keychain First Aid, it ask password and select Verify and start. If found error, try it again and select Repair.