Submit Hint Search The Forums LinksStatsPollsHeadlinesRSS
14,000 hints and counting!

10.4: Fix System Keychain corruption after migration System 10.4
Tiger only hintThis may be a rare glitch, but it's a nasty one: after I used Migration Assistant to move settings and accounts from an old machine to a new one, corruption in the System keychain prevented user keychains from working or being modified.

Situation: I was migrating my account, settings, applications, etc., from an old machine running OS X 10.3 to a new one running 10.4. Everything seemed fine except for a strange Safari bug: it wouldn't make HTTPS connections. Corrupt Keychain entries can cause Safari crashes suggested a reason for the problem. Well, something was definitely wrong with my Keychain. In fact, I couldn't use Keychain Assistant to do anything: attempting to open or repair my existing ~/Library -> Keychains -> login.keychain didn't work, nor could I create a new Keychain. Each attempt produced an error message.

I tried creating a new user to see if that user could use a Keychain. No go: the new user had the exact same problem with Keychain Assistant, and could not create a keychain.

I had previously enabled the root user, so I figured I would log in as root and see if that made a difference in running Keychain Assistant. It did: I was able to select the System Keychain, and determine that it was corrupt via Keychain First Aid. Running Repair in Keychain First Aid then fixed it.

After that, user keychains were accessible, and Keychain Access worked as it should. I can't think of a way to do this repair without enabling the root user, because Keychain First Aid operates on the login keychain only, and only the root user's login keychain is the System keychain.
    •    
  • Currently 3.25 / 5
  You rated: 3 / 5 (4 votes cast)
 
[18,591 views]  

10.4: Fix System Keychain corruption after migration | 8 comments | Create New Account
Click here to return to the '10.4: Fix System Keychain corruption after migration' hint
The following comments are owned by whoever posted them. This site is not responsible for what they say.
10.4: Fix System Keychain corruption after migration
Authored by: rhythmicmoose on Dec 13, '05 09:02:06AM

Couldn't you just launch Keychain First Aid in Pseudo? Wouldn't that open it in the root account and let you make the right fixes?



[ Reply to This | # ]
10.4: Fix System Keychain corruption after migration
Authored by: thekurgan on Dec 13, '05 01:17:05PM

What is pseudo? Is it like sudo as in: "super-user do" or is it another app for running sudo in the gui?

---
-----
If I throw a dog a bone, I don't care to know whether it tastes good or not



[ Reply to This | # ]
10.4: Fix System Keychain corruption after migration
Authored by: _merlin on Dec 13, '05 02:05:02PM

It's a shareware app that works like sudo, but for GUI applications. (On VersionTracker.)



[ Reply to This | # ]
10.4: Fix System Keychain corruption after migration
Authored by: jaydisc on Dec 13, '05 07:49:25PM

No, in this case you would indeed require activating the root account.

You CAN launch Keychain Access with sudo or Psuedo, but when you run the Keychain First Aid command you are prompted for your user/pass. In actuality, you could merely launch Keychain Access as yourself, and run Keychain First Aid with ANY user/pass combo and it will evaluate THAT user's keychains, so root account being active is unfortunately indeed required.... just quickly deactivate it afterwards!



[ Reply to This | # ]
10.4: Fix System Keychain corruption after migration
Authored by: Alain55 on Apr 08, '06 11:58:33PM

Hi, i have just now a similar problem with 10.4.4, newly here i'll try to explain here in english the symptoms
In summary: i did the above trick, but now when i log to my normal admin user name, in keychain i have 2 login keychain "session in french" wich are identic and active, but before, i had fix another keychain named "Trousseau de Alain". It is no more in function : my newly created pass here is on the login keychain. I guess it deals with the "synchronize keychain with login keychain" option but how to clean that ?



[ Reply to This | # ]
10.4: Fix System Keychain corruption after migration
Authored by: Alain55 on Apr 09, '06 12:10:38AM
Début de la vérification Vérification de la configuration du trousseau pour Alain xxxxxxx (ID d'utilisateur = 502)
  • Le répertoire de départ est /Users/Alain
  • Trousseau de session vérifié
  • Mot de passe vérifié pour ~/Library/Keychains/login.keychain
  • Réglages vérifiés pour ~/Library/Keychains/login.keychain
  • Trousseau par défaut vérifié
  • ~/Library/Keychains/Trousseau de Alain.keychain a été défini comme le trousseau par défaut (au lieu de ~/Library/Keychains/login.keychain)
  • Liste de recherche de trousseau vérifiée
  • Contenu de ~/Library/Keychains/login.keychain vérifié
  • Contenu de ~/Library/Keychains/Trousseau de Alain.keychain vérifié
  • Contenu de ~/Library/Keychains/Trousseau de Max.keychain vérifié
  • Des problèmes ont été détectés : veuillez utiliser l'option Réparer pour les corriger
  • Échec de la vérification

    [ Reply to This | # ]
  • 10.4: Fix System Keychain corruption after migration
    Authored by: dklau on May 05, '06 05:54:30PM

    I, too, am new. I have had similar difficulties, and had to use the root/admin user account so that I could abandon a useless system keychain. I was not sure if M Alain55 had found an answer to his problem. I believe that it should be okay to delete the old system keychain, but I am no expert. I would like to point to another discussion that is pertinent because it was why I had to find a way to get around my system keychain in the first place: 10.4: AirPort and System.keychain password solution (http://www.macosxhints.com/article.php?story=20060318124936642). M Alain55, j'espère que vous trouviez quelque chose là dedans à vous aider.

    ---
    You're only paranoid if they aren't out to get you!



    [ Reply to This | # ]
    10.4: Fix System Keychain corruption after migration
    Authored by: dsewell on Jun 08, '06 08:33:41AM

    I'm still having problems even after deleting my old keychain. Every time I restart my system, I have to adopt the strategy of logging in as root and running Keychain Access in order to get my user keychain to work. It's a real pain.

    ---
    David Sewell
    White Hall, Virginia



    [ Reply to This | # ]