• 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: code signing fails to verify on 10.10?
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: code signing fails to verify on 10.10?

  • Subject: Re: code signing fails to verify on 10.10?
  • From: "David M. Cotter via Cocoa-dev" <email@hidden>
  • Date: Wed, 29 May 2019 07:21:30 -0700
well,  the solution was to just re-build the offending library with 10.9 as
the target and all is well

> On May 20, 2019, at 9:38 AM, David M. Cotter <email@hidden> wrote:
>
> i saw this article:
> https://stackoverflow.com/questions/41865537/how-does-apples-codesign-utility-decide-which-sha-algorithms-to-sign-a-shared
>
> <https://stackoverflow.com/questions/41865537/how-does-apples-codesign-utility-decide-which-sha-algorithms-to-sign-a-shared>
>
> which seemed to be related, but the odd thing is that the app launches FINE
> on 10.9, or 10.11 and later.
>
> why fail only on 10.10?
>
>
>> On May 19, 2019, at 8:38 PM, David M. Cotter <email@hidden> wrote:
>>
>> I’m developing on 10.14.4
>> using Xcode 9.4.1
>> signing via command line (not via xcode)
>>
>> my app works fine on 10.12 and above
>> but on 10.10.5, i get this:
>>
>>> Application Specific Information:
>>> dyld: launch, loading dependent libraries
>>> Dyld Error Message:
>>> Library not loaded: @loader_path/../Frameworks/libboost_thread.dylib
>>> Referenced from: /Users/USER/Desktop/kJams 2.app/Contents/MacOS/kJams 2
>>> Reason: no suitable image found.  Did find:
>>>     /Users/davec/Desktop/kJams
>>> 2.app/Contents/MacOS/../Frameworks/libboost_thread.dylib: code signature
>>> invalid for '/Users/davec/Desktop/kJams
>>> 2.app/Contents/MacOS/../Frameworks/libboost_thread.dylib'
>>
>> on the command line of 10.10.5, however, it seems to pass the tests:
>> davec$ codesign -vvvv --deep /Users/davec/Desktop/kJams\ 2.app
>>> --prepared:/Users/davec/Desktop/kJams
>>> 2.app/Contents/Frameworks/Growl-123.framework/Versions/Current/.
>>> --validated:/Users/davec/Desktop/kJams
>>> 2.app/Contents/Frameworks/Growl-123.framework/Versions/Current/.
>>> --prepared:/Users/davec/Desktop/kJams
>>> 2.app/Contents/Frameworks/Growl.framework/Versions/Current/.
>>> --validated:/Users/davec/Desktop/kJams
>>> 2.app/Contents/Frameworks/Growl.framework/Versions/Current/.
>>> --prepared:/Users/davec/Desktop/kJams
>>> 2.app/Contents/Frameworks/libboost_atomic.dylib
>>> --validated:/Users/davec/Desktop/kJams
>>> 2.app/Contents/Frameworks/libboost_atomic.dylib
>>> --prepared:/Users/davec/Desktop/kJams
>>> 2.app/Contents/Frameworks/LAME.framework/Versions/Current/.
>>> --validated:/Users/davec/Desktop/kJams
>>> 2.app/Contents/Frameworks/LAME.framework/Versions/Current/.
>>> --prepared:/Users/davec/Desktop/kJams
>>> 2.app/Contents/Frameworks/libboost_system.dylib
>>> --validated:/Users/davec/Desktop/kJams
>>> 2.app/Contents/Frameworks/libboost_system.dylib
>>> --prepared:/Users/davec/Desktop/kJams
>>> 2.app/Contents/Frameworks/libboost_thread.dylib
>>> --validated:/Users/davec/Desktop/kJams
>>> 2.app/Contents/Frameworks/libboost_thread.dylib
>>> --prepared:/Users/davec/Desktop/kJams
>>> 2.app/Contents/Frameworks/libgnsdk_manager.3.2.0.dylib
>>> --validated:/Users/davec/Desktop/kJams
>>> 2.app/Contents/Frameworks/libgnsdk_manager.3.2.0.dylib
>>> --prepared:/Users/davec/Desktop/kJams 2.app/Contents/MacOS/HelperTool
>>> --validated:/Users/davec/Desktop/kJams 2.app/Contents/MacOS/HelperTool
>>> --prepared:/Users/davec/Desktop/kJams
>>> 2.app/Contents/Frameworks/libgnsdk_musicid.3.2.0.dylib
>>> --validated:/Users/davec/Desktop/kJams
>>> 2.app/Contents/Frameworks/libgnsdk_musicid.3.2.0.dylib
>>> --prepared:/Users/davec/Desktop/kJams 2.app/Contents/MacOS/InstallTool
>>> --validated:/Users/davec/Desktop/kJams 2.app/Contents/MacOS/InstallTool
>>> /Users/davec/Desktop/kJams 2.app: valid on disk
>>> /Users/davec/Desktop/kJams 2.app: satisfies its Designated Requirement
>>
>> and:
>>> davec$ spctl -a -t exec -vv /Users/davec/Desktop/kJams\ 2.app
>>> /Users/davec/Desktop/kJams 2.app: accepted
>>> source=Developer ID
>>> origin=Developer ID Application: David M. Cotter (GZPG2DNS57)
>>
>> so… what gives?
> _______________________________________________
>
> Cocoa-dev mailing list (email@hidden)
>
> Please do not post admin requests or moderator comments to the list.
> Contact the moderators at cocoa-dev-admins(at)lists.apple.com
>
> Help/Unsubscribe/Update your Subscription:
>
> This email sent to email@hidden

_______________________________________________

Cocoa-dev mailing list (email@hidden)

Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com

Help/Unsubscribe/Update your Subscription:

This email sent to email@hidden
References: 
 >code signing fails to verify on 10.10? (From: "David M. Cotter" <email@hidden>)
 >Re: code signing fails to verify on 10.10? (From: "David M. Cotter" <email@hidden>)

  • Prev by Date: Re: Is the list alive?
  • Next by Date: Re: Is the list alive?
  • Previous by thread: Re: code signing fails to verify on 10.10?
  • Next by thread: Crashing in NSTabView
  • Index(es):
    • Date
    • Thread