Codesign non-AppStore build with AppStore signing identity
Codesign non-AppStore build with AppStore signing identity
- Subject: Codesign non-AppStore build with AppStore signing identity
- From: Trygve Inda <email@hidden>
- Date: Wed, 05 Oct 2011 11:15:16 -0700
- Thread-topic: Codesign non-AppStore build with AppStore signing identity
One of our apps (distributed via our website) is not signed. It seems that
Parental Controls signs our app behind our back to do what it does.
This obviously alters our app and breaks some integrity checks.
A Tech Note says that simply signing it will fix this.
Can we just sign it the same way we do the version built for the App Store,
using the same digital signature?
> TN2206
> The Parental Controls, MCX, and Application Firewall subsystems in Leopard,
> when encountering an unsigned program, will ad hoc sign the program in order
> to track its identity from launch to launch. This will usually modify the
> program on disk, and can happen without apparent user input, e.g., when the
> Application Firewall first notices that your program is trying to accept an
> inbound network connection. If your program can be damaged by signing, it is
> imperative that you ship a signed version as soon as practical. Programs
> signed by their manufacturer are not modified in this way.
Thanks,
Trygve
_______________________________________________
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