Creating a certificate authority

Although I haven’t tested a self-signed CA certificate as the SSL server’s certifiate, reading around the web suggests it will not make Firefox 3 happy. Since it doesn’t cost all that much time to do it, let’s generate a certificate authority.

1. Open Keychain Access
2. I’ve had issues with Certificate Assistant using my login keychain, so to avoid any problems, create a new keychain for certificates.
3. 
   Use the Create a Certificate Authority… command from the Keychain Access > Certificate Assistant menu.
4. 
   Enter the name of the CA certificate, select Self Signed Root CA as the type and make sure the Let me override defaults checkbox is checked.
5. 
   Enter the desired serial number and validity period. Firefox 3 will actually remember certificate serial numbers and reject a new certificate with the same serial number as a previous certificate (coming from the same authority, that is), so make sure you’re keeping track of serial numbers.

   The User Certificate Type must be set to SSL Server.

   The other settings are for generating a pretty CA web page to let people make certificate requests for your new authority (you may want to use that), and to sign your certificate invitation.

6. 
   Enter the basic contact information for the CA certificate. The Name (Common Name) field doesn’t have to be a valid domain name, since the CA certificate won’t be used by any server.
7. 
   The default values for this step are fine.
8. 
   This step allows to specify default key pair settings for any leaf certificate you create with the CA certificate as the root. The default values are fine.
9. 
   The CA certificate must have a Key Usage Extension with at least the Signature and Certificate Signing capability bits set. If either one of those capabilities are not specified, Firefox 3 will reject any child certificate of the CA certificate.
10. 
    This step allows to specify default key usage extension settings for any leaf certificate created with the CA certificate as the root. SSL server certificates must have at least the Key Encipherment and Key Agreement capability bits set. If either one of those capabilities are not specified, Firefox 3 will reject the certificate.
11. 
    Although documentation suggests this may not be necessary, giving the CA certificate an extended key usage extension with at least the SSL Server Authentication capability bit set has no serious consequences and provides additional insurance that Firefox 3 will be happy. Note that the default value is All, which should include SSL Server Authentication, but again no harm done in being pedantic.
12. 
    This step allows to specify default extended key usage extension settings for any leaf certificate created with the CA certificate as the root. SSL server certificates must have at least the SSL Server Authentication capability bit set. If that capability is not specified, Firefox 3 will reject the certificate.
13. 
    The CA certificate must have a basic constraints extension with at least the Use this certificate as a certificate authority option specified. If it is not, Firefox 3 will reject any child certificate of the CA certificate.
14. 
    This step allows to specify default basic constraints extension settings for any leaf certificate created with the CA certificate as the root. SSL server certificates must not have the Use this certificate as a certificate authority option specified (while having a basic constraints extension). If the extension is missing or that option is specified, Firefox 3 will reject the certificate.
15. 
    Any certificate with the SSL Server type must have a subject alternate name extension specifying either the dNSName field or the iPAddress field. Obviously there are no special constraints on the value of either of those fields for the CA certificate.
16. 
    Again, any certificate with the SSL Server type must have a subject alternate name extension specifying either the dNSName field or the iPAddress field. The value of those fields must match the domain name or IP address which clients will use to contact SSL servers using any child certificate of the CA certificate. Obviously, we will have to override this value when creating each such child certificate unless we’re creating them for the same server all the time. Nevertheless, Certificate Assistant requires a value to be specified to continue, so provide a reasonable default.
17. 
    Select the keychain in which the CA certificate will be stored. If you want browsers using Keychain Services to accept child certificates of the CA certificate, check the On this machine, trust certificates signed by this CA checkbox. Note that, as the label implies, this will affect the trust setting for the CA certificate for the entire machine, not just your specific system user. Consider the consequences of that choice carefully. It is possible to change trust settings on a per-user basis.
18. 
    Success!

We can finally appreciate the fruit of our labour. Double-clicking the CA certificate in Keychain Access will allow you to confirm that all the required settings, options and capabilities are properly configured. It should look like this:

Creating a SSL server leaf certificate

I will not repeat the entire sequence of operation presented for the CA certificate, but rather focus on the steps that are specific to the creation of a SSL server leaf certificate. Make sure to keep in mind the various restrictions mentioned above concerned leaf certificates, since we have to override the default values we specified during the creation of the CA certificate and Certificate Assistant is not nice enough to fill in those defaults .

1. 
   Use the Create a Certificate… command from the Keychain Access > Certificate Assistant menu.
2. 
   Enter the domain name that clients will be using to access the SSL server as the certificate’s name, and choose Leaf as the certificate type. Make sure to check Let me override defaults since we need to edit some of the certificate’s settings from the defaults we specified earlier.
3. 
   Enter a serial number different than that of the CA certificate and different than that of any other leaf certificate you have already created, even if they were for the same domain. Firefox 3 checks and keeps track of certificate serial numbers and will reject a certificate re-using a serial number. Also make sure that the certificate type is set to SSL Server, otherwise Firefox 3 will reject the certificate.
4. 
   The Name (Common Name) field must match the domain clients will use to connect to the SSL server, otherwise Firefox 3 will reject the certificate.
5. 
   Select the CA certificate created earlier.
6. 
   SSL server certificates must have a key usage extension with the Key Encipherment and Key Agreement bits set. If they are not, Firefox 3 will reject the certificate.
7. 
   SSL server certificates must have an extended key usage extension with the SSL Server Authentication bit set. If it is not, Firefox 3 will reject the certificate.
8. 
   SSL server certificates must have a basic constraints extension with the Use this certificate as a certificate authority option disabled.
9. 
   SSL server certificates must have a subject alternate name extension with either the dNSName field or the iPAddress field specified. The values for those fields should match what clients will use to connect to the SSL server. In order words, the value for the dNSName field should match the value of the Name (Common Name) field of the certificate (specified in step 4) and the value iPAddress field should match the IP address to which the dNSName domain resolves.
10. 
    Success again!

We can once more appreciate the fruit of our labour. Double-clicking the certificate in Keychain Access will allow you to confirm that all the required settings, options and capabilities are properly configured. It should look like this:

Going from the keychain to Apache

As a common scenario, here’s the straightforward way to export certificates stored in a keychain in a format suitable for Apache’s mod_ssl.

1. Select the desired certificate from the Certificates or My Certificates category in Keychain Access (with the containing keychain selected, of course). The certificate item should have a disclosure triangle which once expanded will reveal the certificate’s private key. Indeed, we need to export both the certificate and its private key.
2. Use the File > Export Items… command.
3. 
   Use the Personal Information Exchange (.p12) format to export the certificate.
4. 
   Although you provide a password with which to encrypt the private key, since Apache requires it to be unencrypted in order to start automatically, simply don’t provide any password. You may want, however, to choose a secure export location, such as a private temporary folder that doesn’t get backed up by Time Machine or an encrypted disk image.
5. Open Terminal.
6. Run the following commands to export the certificate and the private key (unencrypted) to OpenSSL’s PEM format which mod_ssl requires.

   openssl pkcs12 -in example.com.p12 -nokeys -nodes -out example.com.crt
   openssl pkcs12 -in example.com.p12 -nocerts -nodes -out example.com.crtkey

All that’s left to do is ship out the .crt and .crtkey files to your SSL server and to securely delete all 3 files (.p12, .crt and .crtkey) from your local computer.

Loose ends because Firefox 3 can’t bother to fully support Mac OS X

When you connect with Firefox 3 to your SSL server with its shiny new certificates, Firefox 3 is still going to give you one of its famous gray error pages, stating that the certificate authority that signed the server’s certificate is not trusted. This is because, unlike every other browser for Mac OS X, Firefox can’t bother to use Keychain Services to verify certificate trust and therefore doesn’t know anything about the CA certificate stored in one of your keychains.

However this is a simple matter to fix. In the same error page, click on the Or you can add an exception… link, then on the Add Exception button. In the dialog that follows, first click on the Get Certificate button, make sure the Permanently store this exception checkbox is checked and finally click on the Confirm Security Exception button.

I’ll take this time to mention that that dialog is so poorly designed, with the Cancel button on the right of the dialog and of the “confirm action” button, contrary to Mac OS X HIG guidelines, not to mention the default button is that Get Certificate button which itself shouldn’t even be there – Firefox 3 should clearly fetch the certificate automatically. End of design commentary .

After that, Firefox 3 will trust the certificate and you should be good to go. You could also export the CA certificate and add it to Firefox 3’s list of trusted roots, an exercise I leave to the reader.

While watching the iPhone SDK announcement video, I noticed some odd things in my beloved Xcode. Some UI elements were looking different. And indeed, the iPhone SDK includes a new version of Xcode (and many other dev tools) which may be of interest for anyone doing Mac OS X development. Some of the highlights:

• Brand-new “New Project” and “New File” dialogs. I really like them, and the new templates make more sense.
• Multi-platform support. Each platform can provide its own set of tools and SDKs. This was obviously added to support the iPhone. So the big picture now is Platforms > SDKs > Architectures.
• Preview of gcc-4.2 and llvm-gcc-4.2. I am really excited to check this two out, particularly the LLVM powered compiler, which brings to Mac OS X developers modern link-time optimization that Microsoft Visual Studio and Intel CC customers have enjoyed for many years now. LLVM is the future of gcc compiler technologies, and it’s great to start seeing that get out into a lot of people’s hands.
• Improved support for conditional build settings (AKA per-architecture build settings).

I hope to see the final version of Xcode 3.1 to be released at this year’s WWDC, if not some manner of new beta release.

Well today, NVIDIA made CUDA available for Mac OS X. This is a sign that times are changing for Apple when they start to make such a kind of inroad. And of course, everyone in the (probably small) Mac HPC business and in the scientific community is probably very happy about this.

So if you own NVIDIA hardware, go grab it and give it a try!

Give it a try. As far as I’m concerned, my only deception so far is not being able to buy a license already.