Re: SecStaticCodeCheckValidity fails when app is lauched from Terminal
Re: SecStaticCodeCheckValidity fails when app is lauched from Terminal
- Subject: Re: SecStaticCodeCheckValidity fails when app is lauched from Terminal
- From: Chris Hanson <email@hidden>
- Date: Tue, 27 Sep 2016 13:39:02 -0700
How are you getting the URL that you pass to represent your application?
Could it be that you’re constructing the URL from a relative path when run from the command line, rather than the full path? (You can’t depend on being run from any particular working directory.)
-- Chris
> On Sep 26, 2016, at 2:44 AM, Markus Spoettl <email@hidden> wrote:
>
> I'm using SecStaticCodeCheckValidity() to self check the signature of my own app when it is launched. This works fine and always has.
>
> All of a sudden, the call to SecStaticCodeCheckValidity() fails if (and only if the application) is started from the Terminal. When I start the very same app from the Dock or from the Finder the check succeeds (iow. the call returns noErr).
>
> I don't know exactly when it started failing. I only know it definitely worked before on previous versions of El Capitan but now it no longer does (v 10.11.6).
>
> Any ideas?
>
> Regards
> Markus
> --
> __________________________________________
> Markus Spoettl
> _______________________________________________
>
> 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