On 2009 May 20, at 23:20, Kevin LaCoste wrote:
The docs clearly state that anything in Contents/MacOS is covered by
the app bundles signature.
Nope. The Code Signing Guide is ambiguous at best on this point, and
so I just sent them feedback "It wasn't helpful".
Also, it does not work ac
Thanks for the pointer Jerry.
My understanding of that message is that you need to manually sign anything
in Contents/Helpers then. The docs clearly state that anything in
Contents/MacOS is covered by the app bundles signature.
Kevin
On Thu, May 21, 2009 at 8:51 AM, Jerry Krinock wrote:
>
> On
On 2009 May 19, at 23:28, Kevin LaCoste wrote:
if we move helper tools into a new Contents/Helpers folder are they
covered by codesign?
The answer is that you must invoke the 'codesign' tool to sign the
helper tool as a separate step in your shipping script, but this is
true regardless o
Hi Kevin,
On Wed, May 20, 2009 at 4:43 PM, Chris Suter wrote:
[snip]
> These are the default rules:
>
> ^Resources/.*\.lproj/
>
> optional
>
> weight
> 1000
>
Sorry, the default rules are more than just that. Have a look at the
end of a generated CodeResources file and you'll the
Hi Kevin,
On Wed, May 20, 2009 at 4:28 PM, Kevin LaCoste wrote:
> Thanks for the link. Now the question becomes, if we move helper tools into
> a new Contents/Helpers folder are they covered by codesign?
No, it wouldn't be covered by codesign. codesign has some built-in
rules that specify what i
Thanks for the link. Now the question becomes, if we move helper tools into
a new Contents/Helpers folder are they covered by codesign? Would the
problem mentioned in that post persist if we used Contents/MacOS/Tools
instead? Sub paths must be supported since it's part of the inspector
window. Time
On 2009 May 19, at 18:21, Kevin LaCoste wrote:
I found some sample code that includes a helper tool and yes, it's
in the
"Contents/MacOS" folder.
Yes, but there are issues with this. Read:
http://www.cocoabuilder.com/archive/message/cocoa/2009/3/26/233141
My privileged helper tool is in
Hey Chris, thanks for the reply.
Some further follow up.
I found some sample code that includes a helper tool and yes, it's in the
"Contents/MacOS" folder. Also, when opening the inspector window for a "Copy
Files" build phase, I noticed there is a popup menu with what I would guess
are the recom
Hi Kevin,
On Tue, May 19, 2009 at 8:04 PM, Kevin LaCoste wrote:
[snip]
> If I understand that correctly, my tool is in the correct place but I'm not
> confident. Should it be in "Contents/MacOS"
Yes.
> or should I add a "Contents/Executable" folder?
No.
> Bonus question. Is the support direct
Hey guys, quick question about storing a helper tool in an application
bundle.
Currently I have a tool that is launched via NSTask stored in the
"Contents/MacOS" folder of my bundle. When reading up on code signing I saw
this in the Code Signing Release Notes for Mac OS X v10.5 document:
"Do not p
10 matches
Mail list logo
