• 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: Code Signing
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Code Signing


  • Subject: Re: Code Signing
  • From: Dave Keck <email@hidden>
  • Date: Sun, 6 Sep 2009 01:34:39 -1000

These files are certainly meant to be there. (If you happen to look in the
bundles of any number of the standard Mac apps, these two resources are
present.) Signing your code should happen at the very last stage of
development; deleting something from your bundle after it's been signed is
wrong.

You didn't say what arguments you're feeding codesign, but if you do a
simple test of your technique on a copy of Mail, using the following
command:

   codesign -d -r- /Applications/Mail\ copy.app

Before you delete resources: "designated => identifier "com.apple.mail" and
anchor apple"
And after: "/Applications/Mail copy.app: code or signature modified"

... which should speak for itself. :)
_______________________________________________

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

References: 
 >Code Signing (From: Peter Hudson <email@hidden>)

  • Prev by Date: Re: Should we release a CGImage created from NSBitmapImageRep ?
  • Next by Date: Re: Composite Array Controller
  • Previous by thread: Code Signing
  • Next by thread: Re: Code Signing
  • Index(es):
    • Date
    • Thread