{"id":297,"date":"2013-03-07T23:30:42","date_gmt":"2013-03-08T07:30:42","guid":{"rendered":"http:\/\/unmitigatedrisk.com\/?p=297"},"modified":"2013-03-22T00:53:28","modified_gmt":"2013-03-22T08:53:28","slug":"advanced-troubleshooting-of-certificate-validation-related-problems-on-windows-part-1","status":"publish","type":"post","link":"https:\/\/unmitigatedrisk.com\/?p=297","title":{"rendered":"Advanced Troubleshooting of Certificate Validation Related Problems on Windows Part 1"},"content":{"rendered":"

The Windows platform for validating X.509 certificates has a feature I don\u2019t see many discuss — its robust logging subsystem.<\/p>\n

This allows a non-developer (and developers) to get insights into what is happening with applications interactions with CryptoAPI 2 and to some degree what is happening inside those APIs.<\/p>\n

To use this feature you must first enable it, the easiest way to do that is via the EventViewer Management Console (eventvwr.msc), once in there you must navigate to the CryptoAPI 2 (CAPI2) node of the viewer:<\/p>\n\n\n\n
\"clip_image001[6]\"<\/a><\/td>\n\"clip_image002[6]\"<\/a><\/td>\n\"clip_image003[6]\"<\/a><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

 <\/p>\n

Once you get there you select Properties on the operational log, which will give you a dialog that looks something like this:<\/p>\n

\"clip_image007\"<\/a><\/p>\n

 <\/p>\n

Once you \u201cEnable Logging\u201d and \u201cApply\u201d the changes, immediately all calls to CryptoAPI will be logged. CryptoAPI is used all the time so by the time you close that dialog you will have some events you can look at:<\/p>\n

\"clip_image008\"<\/a><\/p>\n

 <\/p>\n

The high level view of each event doesn\u2019t tell you much, for example in the above picture we really only know that the action that was being performed with a \u201cBuild Chain\u201d, this particular event corresponds to a call to CertGetCertificateChain<\/a>.<\/p>\n

To really understand what is going on you need to look at the Details tab:<\/p>\n

\"clip_image009\"<\/a><\/p>\n

 <\/p>\n

Here we can see what was passed into a given into that API call, we can see what certificates we passed in by the calling application, what settings they chose when making that call:<\/p>\n

\"clip_image011\"<\/a><\/p>\n

 <\/p>\n

Some other things you can see in this particular API call include what the disposition of the call was and of course what certificate chain was built.<\/p>\n

Every major API in CryptoAPI has logging similar to this, you get to see what is passed in and what came out. Additionally major \u201cobjects\u201d are sometimes logged as well, for example here is an event showing a certificate that CryptoAPI was operating against:<\/p>\n

\"clip_image012\"<\/a><\/p>\n

 <\/p>\n

Another very useful API to be able to look at is CertVerifyRevocation<\/a>, this will be logged in this fashion:<\/p>\n

\"clip_image013\"<\/a><\/p>\n

 <\/p>\n

Some of these events include references to temporary files, for example in this case you see:<\/p>\n

\"clip_image014\"<\/a><\/p>\n

This is a CRL for the \u201cGlobalSign PersonalSign 1 CA \u2013 G2\u201d, its stored in the Time Valid Object Cahce (TvoCache), you can look at this cache with the \u201ccertutil \u2013urlcache\u201d command.<\/p>\n

 <\/p>\n

The events will all tell you which application was the caller and if they are part of a sequence of tasks you get enough information to correlate them and put them in order.<\/p>\n

\"clip_image015\"<\/a><\/p>\n

 <\/p>\n

I won\u2019t go through all of the events but as you can see this is super valuable when trying to figure out \u2013 Why did that application do that?!<\/p>\n

As you might imagine this logging can slow things down and produces a bunch of data so be sure to turn it off when you are done.<\/p>\n","protected":false},"excerpt":{"rendered":"

The Windows platform for validating X.509 certificates has a feature I don\u2019t see many discuss — its robust logging subsystem. This allows a non-developer (and developers) to get insights into what is happening with applications interactions with CryptoAPI 2 and to some degree what is happening inside those APIs. To use this feature you must […]<\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_monsterinsights_skip_tracking":false,"footnotes":""},"categories":[12,3],"tags":[36,24,79,80],"class_list":["post-297","post","type-post","status-publish","format-standard","hentry","category-programming","category-security","tag-cryptoapi","tag-revocation","tag-troubleshooting","tag-x-509"],"_links":{"self":[{"href":"https:\/\/unmitigatedrisk.com\/index.php?rest_route=\/wp\/v2\/posts\/297","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/unmitigatedrisk.com\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/unmitigatedrisk.com\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/unmitigatedrisk.com\/index.php?rest_route=\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/unmitigatedrisk.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=297"}],"version-history":[{"count":0,"href":"https:\/\/unmitigatedrisk.com\/index.php?rest_route=\/wp\/v2\/posts\/297\/revisions"}],"wp:attachment":[{"href":"https:\/\/unmitigatedrisk.com\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=297"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/unmitigatedrisk.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=297"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/unmitigatedrisk.com\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=297"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}