Re: SecStaticCodeCheckValidity fails when app is lauched from Terminal

2016-09-27 Thread Markus Spoettl
On 27/09/16 22:57, Chris Hanson wrote: On Sep 27, 2016, at 1:54 PM, Markus Spoettl wrote: On 27/09/16 22:39, Chris Hanson wrote: 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 comman

Re: SecStaticCodeCheckValidity fails when app is lauched from Terminal

2016-09-27 Thread Chris Hanson
On Sep 27, 2016, at 1:54 PM, Markus Spoettl wrote: > > On 27/09/16 22:39, Chris Hanson wrote: >> 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 ful

Re: SecStaticCodeCheckValidity fails when app is lauched from Terminal

2016-09-27 Thread Markus Spoettl
On 27/09/16 22:39, Chris Hanson wrote: 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

Re: SecStaticCodeCheckValidity fails when app is lauched from Terminal

2016-09-27 Thread Chris Hanson
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, 2

Re: SecStaticCodeCheckValidity fails when app is lauched from Terminal

2016-09-27 Thread じょいすじょん
Have you also tried NSWorkspace for this? > On 2016 Sep 27, at 2:38, Markus Spoettl wrote: > > 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,

Re: SecStaticCodeCheckValidity fails when app is lauched from Terminal

2016-09-26 Thread Markus Spoettl
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 w

Re: SecStaticCodeCheckValidity fails when app is lauched from Terminal

2016-09-26 Thread Gary L. Wade
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

Re: SecStaticCodeCheckValidity fails when app is lauched from Terminal

2016-09-26 Thread Markus Spoettl
On 26/09/16 15:16, Steve Christensen wrote: What is the error code when it fails? OSStatus is -67054, which is errSecCSBadResource. Only happens when launched from the command line. Markus -- __ Markus Spoettl _

Re: SecStaticCodeCheckValidity fails when app is lauched from Terminal

2016-09-26 Thread Steve Christensen
What is the error code when it fails? > On Sep 26, 2016, at 2:44 AM, Markus Spoettl 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()

SecStaticCodeCheckValidity fails when app is lauched from Terminal

2016-09-26 Thread Markus Spoettl
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 fr