Q: Configuration Profile Code-Signing Certificates
Today, I learned that the Code-Signing Certificate used for signing Device Configuration Profiles is _different_ (and much more expensive) than the SSL Certificate used by other Lion Server services.
I understand that these certificates follow a trust _chain_, and that Lion Server creates a default Code-Signing certificate based on the self-signed certificate it creates during setup. Since then, I've replaced my self-signed SSL Cert with a fully verified one.
How can I use OpenSSL to create a Code-Signing certificate based on my purchased SSL Certificate, just like Lion Server did?
Mac OS X (10.7.1)
Posted on Jul 23, 2012 5:24 PM
You're misunderstanding how the trust chain works.
The only entity that can issue secure certificates are certificate authorities. An SSL certificate is not a certificate authority, it's just a certificate.
So you can't "generate" a code-signing certificate from an SSL certificate. An SSL certificate is not part of a trust chain for a code-signing certificate. If you need a code-signing cert, you must have it issued to you by a certificate authority.
(Besides being used for configuration profiles, this would be useful for software developers who want to distribute their code securely...)
That is true.
Posted on Jul 24, 2012 12:19 PM