• 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: SecStaticCodeCheckValidity fails when app is lauched from Terminal
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: SecStaticCodeCheckValidity fails when app is lauched from Terminal


  • Subject: Re: SecStaticCodeCheckValidity fails when app is lauched from Terminal
  • From: Markus Spoettl <email@hidden>
  • Date: Mon, 26 Sep 2016 19:38:01 +0200

It is an OSX Cocoa GUI application. I have always started it from the command line by executing the executable inside the bundle. While this always worked, it no longer seems to.

That said, it didn't occur to me that there's a proper way, by using the "open" command. Thanks for the tip, this works nicely for my purposes!

Regards
Markus

On 26/09/16 19:18, Gary L. Wade wrote:
In what way did you start your app from the Terminal?  Is this
WindowServer-based or a command line app?  Not sure your purpose in starting
from the command line if WindowServer-based, but have you tried launching it
with the open command where the argument is the .app bundle vs possibly another
way like the actual executable?
--
Gary L. Wade
http://www.garywade.com/

On Sep 26, 2016, at 2:44 AM, Markus Spoettl <email@hidden
<mailto: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
<mailto: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
<http://lists.apple.com>

Help/Unsubscribe/Update your Subscription:

This email sent to email@hidden



--
__________________________________________
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


  • Follow-Ups:
    • Re: SecStaticCodeCheckValidity fails when app is lauched from Terminal
      • From: じょいすじょん <email@hidden>
References: 
 >SecStaticCodeCheckValidity fails when app is lauched from Terminal (From: Markus Spoettl <email@hidden>)
 >Re: SecStaticCodeCheckValidity fails when app is lauched from Terminal (From: "Gary L. Wade" <email@hidden>)

  • Prev by Date: Re: Stupid objective-c question
  • Next by Date: Re: Stupid objective-c question
  • Previous by thread: Re: SecStaticCodeCheckValidity fails when app is lauched from Terminal
  • Next by thread: Re: SecStaticCodeCheckValidity fails when app is lauched from Terminal
  • Index(es):
    • Date
    • Thread