Are you using lack of firewall support as an excuse to avoid IPv6?
My dog ate god's plan

Mac users listen up! Enable certificate checking

I hope you've all heard of the events leading to certificate authority Comodo incorrectly issuing SSL server certificates for some high profile web sites. This is disconcerting news, compounded by an announcement yesterday from hacker Ich Sun who claims to have breached a second CA.


Diginotar
Please revoke DigiNotar CA trust too!

If there is a silver lining, Comodo's provided details of the incident, including the affected domain names and serial numbers here. These certificates have been revoked, so users and applications that check certificate revocation status will not be affected by the bogus certificates.

My colleague Craig Watkins at Transcend, Inc. points out that not everyone has revocation enabled and provided a detailed explanation of how Mac OS users can enable this defense on a private mailing list. His explanation and testing is well documented and timely, so I invited him to post it here.

What follows is fully attributed to Craig Watkins. I take no credit except for having the good sense to keep company with really competent people and recognizing an opportunity to share this competence with you:-)

Google, Microsoft, and Mozilla have patched their browsers (by 23 March) to add these specific certs to a blacklist that will never be trusted.  So far Apple has not done this, but that's OK if
everything is working fine with certificate status checking.

The complication is that OCSP and CRL checking is disabled by default in Mac OS (except for Extended Validation "EV" certificates). You should turn it on.  While I don't see a
a big risk to most of us from the Comodo issue, in general it is a very good idea to enable this checking.  To do this on Mac OS 10.6:

- Open Applications -> Utilities -> Keychain Access
- Under Keychain Access menu, select Preferences...
- Select the Certificates tab
- Set "Online Certificate Status Protocol (OCSP)" to
  "Best Attempt"

- Set "Certificate Revocation List (CRL)" to "Best Attempt"
- Set "Priority" to "OCSP"

 

Preferences

You can now lock the login keychain and close Keychain Access.

This will effect your Safari and Chrome browsers because they use the keychain.  Firefox has its own certificate store, and it should already be configured to use OCSP by default.  For Firefox,

- Under the Firefox menu, select Preferences...
- Select the Advanced tab
- Select the Encryption sub-tab
- Click the (Validation) button
- Verify that "Use the Online Certificate Status Protocol" is checked
- Verify that "Validate a certificate if it specifies an OCSP server" is selected
- Leave "When an OCSP server connection fails, treat the certificate as
  invalid" unchecked

  (That's consistent with the "Best Attempt" setting in Keychain Access)

Firefox

 

To see what it looks like when you visit a site with a revoked certificate, visit
 https://test-sspev.verisign.com:2443/test-SSPEV-revoked-verisign.html


Revoked  Safari
 

Your browser should not allow you to go to this site and should report that the certificate is revoked.  You'll notice a stern warning from Firefox, a really stern warning from Chrome, and a quite wimpy warning from Safari.  You should get this warning from Safari and Chrome regardless
of your Keychain Access settings because this site uses one of those EV certificates that I mentioned above.  These certificates have added validation requirements and Mac OS will always attempt an OCSP validation so that your browser can show you that "extra-green SSL bar."

The only downside to this extra checking is possibly a slight delay to perform the request the first time you go to a web site and when the cache expires.  This should be less overhead than downloading a small image, so I'm not worrying about it.

Thanks Craig!

Comments

Feed You can follow this conversation by subscribing to the comment feed for this post.

via Twitter, Christopher Soghoian
(RT by ioerror)

"Each time your browser validates a SSL cert via OCSP protocol, it queries the Cert Authority. If logged, the CA knows where you are surfing."

Be warned that enabling this setting reduced my App Store app to a crawl.


------------------------- NOTE -----------------


There's a discussion thread about this problem.

http://discussions.apple.com/thread.jspa?messageID=13327545

From the thread:

"Switching off certificate checks did solve the problem. However the discussion in that thread suggests that this fix subverts security."

Folks may also want to check out the 'Perspectives' extension for Firefox (CA mismatch detection)

http://www.networknotary.org/firefox.html

as well as recent initiatives by Google such as their 'Cert Catalog' (not meant to be a replacement for OCSP/CRL)

http://googleonlinesecurity.blogspot.com/2011/04/improving-ssl-certificate-security.html

Lots of work ahead to improve PKI infrastructure. In the meantime we don our tfh's.

When I enable this option in Keychain Access, App Store becomes unusably slow. Every page change takes 10 or more seconds. Is that "normal" or is it just happening to me?

@tempelorg

------------------------- NOTE -----------------


There's a discussion thread about this problem.

http://discussions.apple.com/thread.jspa?messageID=13327545

From the thread:

"Switching off certificate checks did solve the problem. However the discussion in that thread suggests that this fix subverts security."

Hi Dave Z,

I downloaded Opera to confirm this. It seems that Opera uses the certificate validation settings as set in the Certificates pane of Keychain access. I gathered this from Help-> search -> "certificate revocation" returns "Changing the validation settings for certificates". I didn't see any explicit method to modify certificate validation in an Opera preference. Is this what you meant in your comment?

Verify your Comment

Previewing your Comment

This is only a preview. Your comment has not yet been posted.

Working...
Your comment could not be posted. Error type:
Your comment has been saved. Comments are moderated and will not appear until approved by the author. Post another comment

The letters and numbers you entered did not match the image. Please try again.

As a final step before posting your comment, enter the letters and numbers you see in the image below. This prevents automated programs from posting comments.

Having trouble reading this image? View an alternate.

Working...

Post a comment

Comments are moderated, and will not appear until the author has approved them.

Your Information

(Name is required. Email address will not be displayed with the comment.)