1,052 karma · joined August 17, 2014
For example, using the root discussed in the article:
1. Download the root cert from http://ctldl.windowsupdate.com/msdownload/update/v3/static/t... (or save it from the browser's certificate viewer)
2. Open certmgr and import it into 'Untrusted Certificates'.
(This just adds it for the current user's store. Could also import into the computer store by running mmc, adding the Certificates snap-in, and specifying 'Computer account' as the target.)
3. Restart browser. Go to https://certplusrootcag1-test.opentrust.com/ - it should say the certificate is revoked.
This only works for browsers like IE and Chrome, that use the Windows certificate store. Firefox has its own so would have to be done separately.
certutil -generateSSTFromWU roots.sst
Then open roots.sst (which defaults to viewing in certmgr) and it will show the whole lot. Or use certutil -syncWithWU to get all the certs individually.Alternatively: download http://ctldl.windowsupdate.com/msdownload/update/v3/static/t... [1], extract the authroot.stl file (which is in PKCS#7 format), use 'certutil -dump' to list all the subject key identifiers therein, and then download them from the same location as authrootstl.cab by appending ".crt" to the identifier.
Windows is not lying about anything, you just need to look in the right place.
Also, if you want to examine the CTL list that Windows is currently using - which should be identical to the one above unless it's brand new or there has been a problem downloading it - this will extract it from the registry:
powershell -Command "[IO.File]::WriteAllBytes('authroot-local.stl',(Get-ItemProperty -Path 'HKLM:\SOFTWARE\Microsoft\SystemCertificates\AuthRoot\AutoUpdate').EncodedCtl)"
Then use 'certinfo -dump' or whatever you like, it's exactly the same format as the downloaded authroot.stl. This is the same registry data that the OP's CTLInfo tool examines.[1] as specified in https://support.microsoft.com/en-us/kb/2677070
If you wish to mask this from the general public, your registrar has instructions here: https://uk.godaddy.com/help/add-private-registration-420
Though of course it doesn't help if the owner of the device is unknown, as alluded to in the linked article.
This was just on amd64 though - installing OpenBSD for i386 seems to work okay, apart from sometimes hanging on boot (not sure why this is).
[pdf] https://bitstampincidentreport.files.wordpress.com/2015/07/2...
[docx] https://bitstampincidentreport.files.wordpress.com/2015/07/2...
Fortunately, they left libgen (http://gen.lib.rus.ec/) unblocked - as they weren't concerned about copyright issues, only malware threats - which has an entire searchable mirror of all papers and books downloaded via sci-hub. It's a fantastic, incredibly useful resource and I hope it continues to operate unscathed.
Alternatively, one could enter information that looks plausibly valid but is in fact completely invented. How often does one receive articles in the mail or phone calls to the whois contact points anyway? As far as I've experienced, any communication is to the email address. I suppose it depends what the penalties are if you're somehow found out.