Code Signing and Replacement Certificates?
Code Signing and Replacement Certificates?
- Subject: Code Signing and Replacement Certificates?
- From: Karl Moskowski <email@hidden>
- Date: Wed, 22 Apr 2009 12:02:11 -0400
Suppose I release a Leopard application signed with a valid code
signing certificate (not self-signed). Whenever I release a new
version, the application firewall doesn't nag about allowing
connections, and the app has unfettered access to keychain items
created in previous versions.
What happens when my certificate expires and I get a new one with the
same name from the issuer? If I release a new version signed with the
new certificate, will the warning dialogs asking for the various
permissions reappear?
As a possibly complicating factor, my app includes a signed launch
daemon that won't be allowed to present the usual nagging to a user,
AFAIK.
TIA.
----
Karl Moskowski <email@hidden>
Voodoo Ergonomics Inc. <http://voodooergonomics.com/>
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