My Google Chrome installation on Snow Leopard is asking for access to the keychain any time I go to a site with login information... This happened really suddenly - I've restarted and tried different combinations of settings (always allow) to no avail. The suggestions here: Safari keeps asking permission to access the keychain. have not solved my problem. Any advice?

7 Answers
7

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.

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.

Worked! Looked like my sync now isn't working but I will research that..
–
MarcusJun 23 '12 at 15:10

My problem wasn't that it asked for passwords for new sites but that I had to click through a whole bunch of "do you want to..." when starting Chrome. Solution was to delete the entry in Keychain access and then restart Chrome. I have to reenter all passwords now but that is only fair - if I tell my users to do it I should be able to do it myself too.
–
LosManosJun 16 '14 at 7:22

What fixed it for me is moving the Google Chrome keychain entry from a secondary keychain into my primary keychain. I have multiple keychains due to poorly moving my keychain database from system to system and moving it into the "master", or "primary", database fixed the issue.