Re: code signing on the command line
Re: code signing on the command line
- Subject: Re: code signing on the command line
- From: James Walker <email@hidden>
- Date: Wed, 06 Aug 2014 13:57:31 -0700
On 8/5/2014 7:07 PM, Jerry Krinock wrote:
On 2014 Aug 05, at 17:06, James Walker <email@hidden>
wrote:
codesign -s my-identity myapp.app
The trick was to use Xcode to sign some app and copy the long
cryptic parameters it sent to codesign. Is that still the case in
Mavericks and Yosemite?
Yes, this still works for me, except what you are missing in your
command line there is not “cryptic”. It’s a string of “designated
requirements”, and this string has been published in the archives of
email@hidden. Or you can ferret them out of lines
2209-2233 in the script that I published a link to earlier today,
https://gist.github.com/jerrykrinock/b3ec9422e97f99895eea.
I don't mean to be ungrateful, but I wasn't asking whether this still
works, but whether it's still *necessary*.
I refreshed my memory of the need for specifying requirements, and it
was about compatibility with Snow Leopard. So as an experiment, I
signed an app on Yosemite with a command line that did not specify
explicit designated requirements, then moved it to Snow Leopard and did
codesign -vvv . It said the signature was valid and satisfies its
designated requirement. So it looks to me like the answer is No, it's
no longer necessary.
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden