> On Jan 27, 2016, at 4:10 PM, Alex Zavatone <[email protected]> wrote: > > I’m wondering if it’s using the system keychain or your login keychain.
It can’t be using the system keychain; that’s only for system-wide data, not any user passwords/keys/certs. > If your certs are empty, that certainly indicates that part of the app > signing will fail. > The exact problem is that even if you have installed a cert, you will need to > export your private key and create the .p12 file for that cert to be > recognized as being part of your keychain (as I found out last night). I think what you mean is that the private key corresponding to the cert needs to be in your keychain too, so that you can sign data with it. If you requested the cert on that machine then the key will already be created there as part of the request, but otherwise you have to export the key+cert as a .p12 file from where it was created, and then import that file on the machine where you want to use the cert. (Sorry, I’m a bit of a crypto geek…) > In any case, Ron Roche wrote an book that was my code signing bible before > Xcode got more advanced and chapter 3 is pure gold for addressing these some > of these problems. I have that book too, but everything’s changed around so much (at least at the Xcode level) since then, that I’ve been figuring the book will cause me more confusion. Anyways, I appear to be dead in the water right now. Even if I remove the certs from my keychain and request/generate new ones, they still don’t show up in “My Certificates” and I get the same error from the codesign tool. —Jens _______________________________________________ Do not post admin requests to the list. They will be ignored. Xcode-users mailing list ([email protected]) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/xcode-users/archive%40mail-archive.com This email sent to [email protected]
