JP Hansen

Q: Keychain Access - can't enter password in First aid.

Hi all

 

After installing El Capitan I have a BIIG problem.. For some reason the password field in first aid in Keychain Access is suddenly missing. I get the following error when trying to run it anyway:

 

Repair started

Checking keychain configuration for jphansen (user ID=501)

Home directory is /Users/jphansen

Checked login keychain

Checked settings for ~/Library/Keychains/login.keychain

Keychain can't be unlocked automatically. Please attempt to unlock ~/Library/Keychains/login.keychain from Keychain Access.

Unable to change password for ~/Library/Keychains/login.keychain. Please change password using Edit > Change Password for Keychain.

Checked default keychain

Checked contents of ~/Library/Keychains/login.keychain

No problems found

Repair completed


And at the same time the login keychain locks..

 

I can change the password but it doesn't make a difference.. I have tried disabling iCloud keychain and throw out the "XXXX-C137-55C9-8894-8900F6509C72" folder. Restarted in Recovery mode and disabled Rootless to see if that made a difference.. It didn't.

 

Anyone else have this issue.. or know how to fix it?

 

I also get a ton if these msgs in the console:

01/10/15 11:32:02,693 secd[569]:  securityd_xpc_dictionary_handler SocialPushAgent[608] copy_matching Error Domain=NSOSStatusErrorDomain Code=-34018 "client has neither application-identifier nor keychain-access-groups entitlements" UserInfo={NSDescription=client has neither application-identifier nor keychain-access-groups entitlements}

 

01/10/15 11:40:16,021 secd[569]:  securityd_xpc_dictionary_handler cloudd[589] copy_matching Error Domain=NSOSStatusErrorDomain Code=-50 "query missing class name" (paramErr: error in user parameter list) UserInfo={NSDescription=query missing class name}

 

01/10/15 11:40:16,021 cloudd[589]:  SecOSStatusWith error:[-50] Error Domain=NSOSStatusErrorDomain Code=-50 "query missing class name" (paramErr: error in user parameter list) UserInfo={NSDescription=query missing class name}

 

01/10/15 11:42:13,827 Keychain Access[1148]: Failed to connect (_showExpiredCerts) outlet from (KeychainApp) to (NSMenuItem): missing setter or instance variable

 

The problem seems to be on both my iMac and Macbook Pro :-/

Macbook Pro 17" Unibody, Mac OS X (10.6)

Posted on Oct 1, 2015 2:55 AM

Close

Q: Keychain Access - can't enter password in First aid.

  • All replies
  • Helpful answers

first Previous Page 4 of 4
  • by applmers,

    applmers applmers Nov 7, 2015 11:08 PM in response to archaic_606123
    Level 1 (0 points)
    iWork
    Nov 7, 2015 11:08 PM in response to archaic_606123

    I am not a tech expert but I was sufficiently frustrated by Keychain Access not working under El Capitan that I may have stumbled upon some workarounds.  Maybe this is stuff I should have known.

     

         Lock your keychains before running Keychain First Aid (KFA).

         KFA is third down under the Keychain Access tab or pulldown when you have the Keychain App open.

           

         If you have more than one keychain: I have one called “login” and another with my name.

         When you run KFA put the name of your keychain in the field labeled user name.  Ex: login goes in the user field when I want to check that keychain’s health

         Run Verify & then if necessary or for insurance run Repair

     

         At one point I must have had a lot of corruption because I couldn’t even Verify or Repair any of my keychains.

         I did a global search of my computer for anything with Keychain as the main word.

         BTW I have never found Spotlight a good search mechanism and as result do command+F

         Maybe Apple will issue a fix.

         I particularly looked for preference files (Library)

        

         Then I went to my Time Machine and picked a version of each file I planned to delete and restored it from my backup.

     

         If you want to see the password of a particular application and clicking the show password button results in the beach ball twirl, lock your keychain and then follow the prompts for entering your password.  Do this each time.

     

         Admittedly these workarounds are cumbersome and hopefully Apple will address and soon. 

         I had spent a screen sharing session with Apple which ultimately did not resolve my issues.

         Fingers crossed that my workarounds will hold until they fix.

       

    An observation: Since El Capitan there seem to be a large number  of passwords (maybe 15) added to one of my keychains.  This recalls the nightmare days of me.com  with lots of bloat. Anyway I get popups asking for passwords I know nothing about.

     

    I’m kicking myself for updating to El Capitan rather than waiting 3-6 mos.  While this password app has been the most serious problem to date there are lots of other niggling problems that guzzle my time.

  • by SiHancox,

    SiHancox SiHancox Nov 8, 2015 1:09 AM in response to applmers
    Level 2 (248 points)
    Mac OS X
    Nov 8, 2015 1:09 AM in response to applmers

    Would advise on not running "Repair" or even putting anything else in the "User" field other than what automatically appears, if you do you will get message stating Keychain First Aid has detected problems but is unable to repair, then if you run either Verify or Repair in the future even leaving what it auto infills in the User field you still appear to get the same error warning.

     

    If you leave User field for Keychain First Aid to infill and only run "Verify" you still get "unable to unlock auto..." message but at least it ends by stating "no problems found" - whether that's from not being able to unlock so can't really check for issues or in fact there truly isn't any, not sure.

     

    As I posted back on 7th Oct, would not trust Keychain to run Repair at the moment just incase it makes things worse, also if everything is running fine (other than a missing Password Field) and you are not running Time Machine would advise you make a simple backup by going to ~/Library and copy "Keychains" folder to a safe location - if a problem occurs in the future you just trash and copy back.

     

    Lastly, although my Bug Report was closed out on 20th Oct with "Engineering has determined that your bug report is a duplicate of another issue and will be closed" - the duplicate is still showing as being open and one presumes being worked on.

  • by 4NDY17,

    4NDY17 4NDY17 Nov 8, 2015 2:35 AM in response to 4NDY17
    Level 1 (0 points)
    Nov 8, 2015 2:35 AM in response to 4NDY17

    It seems most people have missed the original point in this thread. He and I were never experiencing any wifi issues. For you people who are I suggest turning your energy to another subject of OS X. If you have cleanly erased the Mac, replaced the router, used the correct encryption and remove all signs of interference test with another Mac and then submit your issue with AppleCare. I won't divulge what I used to do nor what I currently do now at the risk of some know it all making themselves look stupid. Let's just say I have a certain degree of knowledge  in this field.

     

     

    My issue simply that the password field is missing. I have checked over 20 macs running 10.11.1 and all of them (including ones that were factory installed and ones that had iCloud Keychain off. EVERY SINGLE ONE had this "feature". This now appears to be expected behaviour and I will be marking this as resolved as my keychain works. With or without iCloud. As for your iUlcer, like i said. Get a PC. I'm sure it will sync really well with your Samsung phone.

  • by JP Hansen,

    JP Hansen JP Hansen Nov 9, 2015 1:31 AM in response to 4NDY17
    Level 1 (0 points)
    iPad
    Nov 9, 2015 1:31 AM in response to 4NDY17

    True.. To cut it out.. Here is my issue:

    Keychain Access First Aid problem.png

    Screen Shot 2015-11-09 at 10.25.29.png

     

    And here is the errors from the log:

     

    09/11/15 10:30:26,200 Keychain Access[8384]: PAM: Unable to authenticate.

    09/11/15 10:30:38,288 Keychain Access[9076]: Failed to connect (_showExpiredCerts) outlet from (KeychainApp) to (NSMenuItem): missing setter or instance variable

    09/11/15 10:30:38,639 Keychain Access[9076]: Failed to connect (_modified) outlet from (KeyPreview) to (NSTextField): missing setter or instance variable

  • by 4NDY17,

    4NDY17 4NDY17 Nov 9, 2015 2:11 AM in response to JP Hansen
    Level 1 (0 points)
    Nov 9, 2015 2:11 AM in response to JP Hansen

    Hmm. I am yet to check my logs. But  i bet will see them too.

     

    Your keychain appears to be working. Those logs actually point out the text field is missing. I believe the privliges of the key chain app have been changed. When repairing you used to be able to input the Password of the account in  the app. we now receive a prompt from another process that may require Admin privileges to perform the task. We would be best to ask this question to a developer. Maybe that linc guy can help. He seems pretty cluey.

     

    https://discussions.apple.com/people/Linc+Davis

  • by SiHancox,

    SiHancox SiHancox Nov 9, 2015 6:44 AM in response to JP Hansen
    Level 2 (248 points)
    Mac OS X
    Nov 9, 2015 6:44 AM in response to JP Hansen

    I see the same two "Failed to connect" but not "Unable to authenticate", instead I get a Sandbox note that indicates a "deny (1) file-read-data" whatever that means!

     

    I wouldn't mind guessing that this issue with Keychain has something to do with Apples new file security system (think it's call SIPS) that as I understand puts a new and better level of security around system files so they can not be altered or deleted.

  • by JP Hansen,

    JP Hansen JP Hansen Nov 9, 2015 7:25 AM in response to SiHancox
    Level 1 (0 points)
    iPad
    Nov 9, 2015 7:25 AM in response to SiHancox

    If you mean Rootless - I have disabled it? So I guess thats not the case..

  • by SiHancox,

    SiHancox SiHancox Nov 9, 2015 7:57 AM in response to JP Hansen
    Level 2 (248 points)
    Mac OS X
    Nov 9, 2015 7:57 AM in response to JP Hansen

    You might be correct, but not sure disabling Rootless lifts all the protection, it certainly allows "unauthorised" programs to be installed but as far as allowing changes in the system area - not sure. Whatever the reason for the Keychain issue, suppose it's a waiting game until Apple comes out wth a fix.

  • by tetardbleu,

    tetardbleu tetardbleu Nov 9, 2015 5:38 PM in response to JP Hansen
    Level 1 (0 points)
    iPhone
    Nov 9, 2015 5:38 PM in response to JP Hansen

    Hi,

    Exactly the same problem as you all. As it seems we are not alone, I think we can hope for a fix soon. Until then i tried everything mentioned in the four pages for nothing. so, if someone finds what's happening please share!

  • by talyiana,

    talyiana talyiana Nov 24, 2015 8:20 PM in response to tetardbleu
    Level 1 (0 points)
    Nov 24, 2015 8:20 PM in response to tetardbleu

    Same problem as all of you too!

  • by SiHancox,

    SiHancox SiHancox Dec 8, 2015 11:34 PM in response to talyiana
    Level 2 (248 points)
    Mac OS X
    Dec 8, 2015 11:34 PM in response to talyiana

    Not sure if this has happened for all but appears they have sorted the missing Password Field in Keychain First Aid under 10.11.2 update - by removing Keychain First Aid! Can't find it now under the preferences section so Apple must consider it no longer necessary to run any more (probably like Repair Permissions has been removed from Disk Utility).

  • by tetardbleu,

    tetardbleu tetardbleu Dec 9, 2015 10:38 AM in response to SiHancox
    Level 1 (0 points)
    iPhone
    Dec 9, 2015 10:38 AM in response to SiHancox

    Same here. We can reasonably assume your guess is correct. if not, the function will come back when repaired.

first Previous Page 4 of 4