17 February 2011

How to validate the Subject Key Identifier (SKI) from a X509 certificate

Some days ago I received an odd complain that some of the Root CAs we use had the wrong Subject Key Identifier (SKI). I knew that the claim was false but I also knew that I'll have to prove it. The guy did dig on our own specifications and calculated the SKI as we required, the hash of the certificate public key but unfortunately the identifiers did not match.

In order to reproduce the problem I extracted the public key of the Root CA, converted to DER, hashed it with SHA1 and verified that indeed the hash did not match. Let’s do a demonstration of what I did with a public available Root CA:



Now let's calculate the SHA1 of the public key:



As reported, both hashes did not match!

At this point I was a bit confused and decided to read some documentation before moving forward. After some reading I found the answer in the 4.2.1.2 section of the the RFC3280 “Internet X.509 Public Key Infrastructure - Certificate and Certificate Revocation List (CRL) Profile ” (http://www.ietf.org/rfc/rfc3280.txt)



In our case we use method 1) for the SKI but in my calculations I was taking into consideration the whole public key, including tag, length, etc, while I should have used the key bits only.
With the following command I was able to locate the “BIT STRING” with the naked key:



And I only need to extract it and put it on a file in DER format:



The remaining part was to calculate the SHA1 hash which was the same as the SKI:



The same method was used to verify the SKI of a Root CA using SHA256 as a hashing algorithm.

9 comments:

  1. Very informative, thanks a lot!

    ReplyDelete
  2. Thanks for this, i was trying to find a way i could check mine, a couple of people had reported issues

    ReplyDelete
  3. fyew, that's kinda complicated, thanks a lot for explaning that

    ReplyDelete
  4. Anonymous4/8/12 09:52

    This is great, thank you for sharing -- Gowhar Jan.

    ReplyDelete
  5. This comment has been removed by the author.

    ReplyDelete
  6. Very interesting as well as useful article. I was looking for this detail with the help of which I can easily perform this task. Thanks for explaining each step.
    digital certificates

    ReplyDelete
  7. This comment has been removed by the author.

    ReplyDelete
  8. This post has made my day. Had been struggling for weeks

    ReplyDelete