The problem with the ability to use code for my key

I am using El Capitan and Xcode 7.1, I am trying to create and archive an application for upload to the application store. After compilation, this warning appears: enter image description here

Buttons

but Always Allow and Allow do not work at all, but Deny cancels the warning! How can I fix this problem? I am using the new iMac and transferred all the data from my old mac to the new one. This problem even occurs with Safari when a website wants to access a password from a keychain.

This is the console log:

SecurityAgent [1476]: ignore user action because the dialog received events from an untrusted source

I reviewed this question , but I'm not sharing anything!

+5
source share
3 answers

Found a solution:

Third-party utilities, such as Alfred, TextExpander, or MagicPrefs, may appear to perceive the "control" of the window in relation to the OS. You can find the culprit by disabling them all and turning them on one by one until you find one (or more) that affects Keychain in this way. Credit: https://apple.stackexchange.com/questions/212622/keychain-wont-let-copy-passwords-after-10-11-1-update

In my case, I just uninstalled the MagicPref application and the problem was solved

+7
source

Not sure if you already understood this, but I ran into this exact problem the other day. Is your Xcode creation block removed? Is ARD / VNC enabled? Apple recently released an update for CVE-2015-5943, “Malicious software can manage key chain access requests programmatically,” which made it so that the always allow / allow buttons do not work, using VNC / ARD. Another thing that can cause this error is applications that change system input, such as Smoothmouse or MagicPrefs.

You can get around this by re-importing the private key and trusting the binary binary code upon import. If you do not have the original .p12 private key file, you can export it from your keychain. You will want to remove the private key from the keychain before re-re-optimization (make sure you have a private key, somewhere first!).

To import and trust the codeign binary, you can use this command.

 security import /tmp/my-cert-path.p12 -k /Users /xcodeuser/Library/Keychains/login.keychain -P mysupercoolprivatekeypassword -T /usr/bin/codesign 

If you need to continue adding trusted applications to the private key, I will definitely keep your developer private keys backed up elsewhere from here. If you lose your private key and cannot export it from Keychain Access, think that you may need to restore it if you do not have local access to this kernel (we use remote hosting Mac Mini).

The log entry you entered is correct.

 SecurityAgent[1476]: Ignoring user action since the dialog has received events from an untrusted source 

'About OS X El Capitan 10.11.1 Security Content, Yosemite Security Update 2015-004 and Mavericks Security Update 2015-007' https://support.apple.com/en-us/HT205375

Other people face one problem:

El Capitan + Xcode 7.1 does not allow me to subscribe to a corporation

https://superuser.com/questions/1004881/osx-10-11-1-keychain-access-does-not-allow-change-to-access-permission

http://nerdanswer.com/answer.php?q=1181710

+5
source

I had the same problem, and I searched for a very long time. I really found this answer, having a similar problem in a popup window on Microsoft Word that won't work.

The fix I used was to restart the computer and turn it on in safe mode ( https://support.apple.com/en-us/HT201262 ), open Xcode (you may need to install the components), and try Archiving it again. This time, when you click Always Allow, it should work.

Hope this helps!

-one
source

All Articles