AW: OS X codesigning best practise?

[Tiemo Hollmann TB]

FYI to answer my own questions:
1. the --deep option in codesign seems to be not valid anymore since
Mavericks, so if you are using apples codesign tool, you really have to
codesign each single component from inside to outside step by step.
2. Yes App Wrapper does it in one step, I will go on with App Wrapper, it's
super easy.
3. I have asked Runrev and it is ok with them, if I codesign runrevs bundles
included in my app.
Tiemo


> -----Ursprüngliche Nachricht-----
> Von: use-livecode [mailto:use-livecode-bounces at lists.runrev.com] Im
Auftrag
> von Tiemo Hollmann TB
> Gesendet: Mittwoch, 10. September 2014 18:21
> An: 'How to use LiveCode'
> Betreff: OT: OS X codesigning best practise?
> 
> Hello,
> 
> I am just trying the first time to codesign my app on OS X 10.9, the
> certificate I bought already.
> 
> When using the command line codesign utility, it seems that I have to
codesign
> each .bundle and .app, which is included in my app first, before I can
> codesign my app itself.
> 
> 1.       Is this correct to do all codesignings as single steps, or is
there
> an option to codesign a complete package with all included components in
one
> step?
> 
> 2.       Do codesigning tools like app wrapper do this job in one step, or
> do I also have to sign all components myself?
> 
> 3.       What about the owners rights? E.g.if my app contains the
> revxml.bundle or another third party external and I would codesign this
rev
> bundle with my certificate, may I do this? If not, what is the
alternative?
> 
> 
> 
> Thanks for your experience
> 
> Tiemo
> 
> 
> 
> 
> 
> 
> 
> _______________________________________________
> use-livecode mailing list
> use-livecode at lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your
subscription
> preferences:
> http://lists.runrev.com/mailman/listinfo/use-livecode