• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: Strange issue with version2 code-signing
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Strange issue with version2 code-signing


  • Subject: Re: Strange issue with version2 code-signing
  • From: Jerry Krinock <email@hidden>
  • Date: Wed, 29 Oct 2014 20:05:36 -0400

> On 2014 Oct 29, at 18:05, Stephen Kay <email@hidden> wrote:
>
> Why would I get "main executable failed strict validation" on an unsigned
> app, yet it allows me to replace a v1 signature with no errors?

I don’t know.  Maybe the new codesign tool doesn’t know how to find all of the signature-required components of your Carbon app.

> OK, but then have I come up with a workaround that allows me to leave
> things the way they are? Just codesign it with v1 first and then replace
> it with v2?

Yes.  With Xcode 3.2 and 10.6.8, you should just close your eyes and be happy that it works.  Your time would be better spent on a long term plan to move on from there.


 _______________________________________________
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


References: 
 >Strange issue with version2 code-signing (From: Stephen Kay <email@hidden>)

  • Prev by Date: Strange issue with version2 code-signing
  • Next by Date: Back-compatibility
  • Previous by thread: Strange issue with version2 code-signing
  • Next by thread: Back-compatibility
  • Index(es):
    • Date
    • Thread