site_archiver@lists.apple.com Delivered-To: installer-dev@lists.apple.com Dkim-signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=messagingengine.com; h=date:subject:from:to:message-id:in-reply-to:mime-version:content-type:content-transfer-encoding; s=smtpout; bh=RdtXwV74GeG6Ucmj20H1o+EsdKo=; b=qllhr83j7/CRooxrkhNYh/tLgsZhNgS+JWm8TKMGUDn88W4p4HgVKs7+3sf+r4uJ12lOLnuAV2C5BLhjeZju2AyTGcOSwY8KKW8MZeYRkyWrIkhOC/ivroNW58NwR0+R3oJPqLBJu9bq650NsPpeIUZomkzqlCGb8TqkymWlnmE= Thread-index: AcrQJ9gFdpy3fLOmBE+bScVsnYGh0w== Thread-topic: What kind of certificates to use for packages? User-agent: Microsoft-Entourage/13.4.0.100208 I would expect that a certificate signed by any certificate authority that is trusted for signing in the System Roots, System, or login keychains would work, at a minimum. Users and admins can import CAs and certificates and trust them for themselves and system-wide, respectively. Then, given my recent experience with building installer packages, my expectations are often dashed quite resoundingly even when there does seem to be documentation and precedent. I had asked something about signed packages on the Apple-CDSA mailing list on 1/27/2010 -- I know dev.iceberg was involved in that thread -- but that didn't indicate anything about any CA requirements. In that thread, Ken McLeod used a test certificate to sign a package but didn't indicate how it was or wasn't related to a CA -- or the kind of CA. -- Jeremy _______________________________________________ Do not post admin requests to the list. They will be ignored. Installer-dev mailing list (Installer-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/installer-dev/site_archiver%40lists.a... This email sent to site_archiver@lists.apple.com