Re: Leopard Codesign - no such identity
Re: Leopard Codesign - no such identity
- Subject: Re: Leopard Codesign - no such identity
- From: Joseph Heck <email@hidden>
- Date: Thu, 13 Dec 2007 15:01:58 -0800
I don't know the right answer here - but I do know that the VeriSign code signing cert that you typically use with WIn32 code (called "Windows Authenticode") isn't the same kind of cert setup that you use to sign Java code or XUL Firefox critters. They're similiar, and functionally very close - but the specifics of the formats aren't identical.
-joe
On Thursday, December 13, 2007, at 02:57PM, "Keith Lund" <email@hidden> wrote:
>I'm preparing my code for Leopard and going through the process of code
>signing my apps. Apple's tutorial worked fine for me when I created a self
>signed certificate.
>
>http://developer.apple.com/documentation/Security/Conceptual/CodeSigningGuid
>e/CodeSigningGuide.pdf
>
>My company has a certificate from VeriSign that they have been using to sign
>the Windoz code. I imported that certificate (MSCV_VSClass3.cer) into the
>Keychain. The name in the Keychain shows up as "Class 3 Public Primary". I
>also changed the "Code Signing" to "Always Trust" under the trust triangle
>in the info about the certificate.
>
>>codesign -v -s "Class 3 Public Primary" /mysoftware
>>Class 3 Public Primary: no such identity
>
>Is it something simple I'm doing wrong?
>
>Thanks
>
>Keith
>
>VeriSign tech support wasn't sure their certificate could be used on a Mac.
>A certificate should work on all platforms. Right?
>
> _______________________________________________
>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
>
>
_______________________________________________
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