Re: GUI for codesign tool?
Re: GUI for codesign tool?
- Subject: Re: GUI for codesign tool?
- From: Chris Suter <email@hidden>
- Date: Wed, 23 Jan 2008 11:57:38 +1100
On 23/01/2008, at 10:45 AM, Bill Cheeseman wrote:
on 2008-01-22 5:05 PM, Chris Suter at email@hidden
wrote:
I had the impression that you weren't supposed to have helper tools
in
the Resources folder any more. I'm told this was stressed most
clearly
in the 2007 WWDC code signing session (according to my colleague who
has seen them—I haven't seen them myself).
I must have missed that session. I'll see if I can catch it online.
But my sense of the documentation I've been reading the last few
days is
that there is nothing wrong with doing this.
In fact, I can't think of any other way I can accomplish what I need
to
accomplish. I have to run a very quick in-and-out operation with a
helper
application that runs as root in order to authenticate and make my
main
application "trusted" by the Accessibility API, then run another
quick app
to terminate the main app and relaunch it to make its new "trusted"
status
effective. If I recall correctly, the security APIs indicate that
authentication operations should be run like this. It certainly
works like a
charm.
Oh, I wasn't suggesting you don't use a helper tool. I was just
suggesting that you shouldn't put them in the Resource folder. I think
you're supposed to put them in the Contents/MacOS folder now. Use -
[NSBundle pathForAuxiliaryExecutable:] to get paths.
Everything in the Resources folder is signed (well almost everything).
There's obviously no need for your helper tools to be there because
they are independently signed.
- Chris
Attachment:
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________
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