Certificate.KeyUsage.IsDecipherOnlyEnabled

But in my certificate the DER BITSTRING is set to B1 (10110001). This means Decipher Only bit is not set and should not be considered (actual DER coding is like this 030200b1 . For a NamedBitString unused/unset trailing bits are removed before encoding. )

So I wondered why CAPICOM is showing it as true when this bit is not set. I looked up into capicom.dll and found this:

CKeyUsage::get_IsDigitalSignatureEnabled and CKeyUsage::get_IsDecipherOnlyEnabled are both set to same address of the function implementation and it looks like code inside returns DigitalSignature flag bit.

Because in my certificate DigitalSignature bit is set, I’m getting back true even for “DecipherOnly” flag. GAAAH!!!

You can download them at SDL tools.

Update: Damn! BinScope requires .NET 3.5 framework. So Win2000 is ruled out!! Unfortunately we are still using Windows 2000 at office.

I got back to the problem later and there was no other way to delete this vc70.idb file. Name shows up in the explorer but just cannot get rid of these files. Our IT support guys were told about the problem and they came down, struggled for few hours and finally left saying they will escalate to IBM team. I did not wait for them because I know they will take few weeks to solve this.

So I decided to solve this myself with ever useful sysinternals tools. Solving this issue was trivial.

1. I fired up filemon.exe from sysinternals.
2. I opened explorer and tried deleting this “vc70.idb” file.
3. Stopped filemon capturing. Filemon shows the actual file location vc70.idb points to in the clearcase view. It leads to something like
“\\networkshare\csv_view.vws\.s0018\80000eabbglslvc70.idb”
4. Now it is trivial: open notepad and save the file with the same name shown by filemon in that location.
5. Go to explorer and simply delete the file!! voila!!

Just in case if you are that unlucky one and have not got 6.70.05.0 version with you, I digged out a link which seems to work:

hxxp://cert.sjtu.edu.cn/download/mdt/dbg_x86_6.7.05.0.exe

I need to get MD5 hash from Volker since he has original one from MS. I’ll then update this post just to make sure Chinese website has not modified it in anyway.

set BUILDNUM=%1

“C:\Program Files\Debugging Tools for Windows\symstore.exe” add /r /f “<path-to-your-prod-symbols-in-the-build>\*.pdb” /s \\<path-to-symbol-store-folder> /t “My Product Name” /v “Build %BUILDNUM%”

Developers can then append path to existing symbols path:

SRV*C:\WinSymbols*http://msdl.microsoft.com/download/symbols;<path-to-your-symbol-store-folder>

If some product is buggy and you don’t want symbols of it anymore, you can use Symstore to remove by using ID. This ID can be found in “<path-to-your-symbol-store-folder>00Admin” folder.  “History.txt” in this location will also show the date when storing is done and corresponding ID.

Advantage using symstore is, needless to say, you don’t have to worry about looking for right symbols when debugging your product. WinDbg resolves it for you

http://msdl.microsoft.com/download/symbols/debuggers/dbg_x86_6.10.3.233.msi