I've recently found a very nonobvious solution for a Microsoft CryptoAPI issue. Because of a read-only flag on the (seemingly unrelated) CREDHIST file, the whole CryptoAPI stack was wildly misbehaving, from CryptAcquireContext() upwards. For the greater common good, I'd like to see this documented in MS KB, where it belongs.
From my past exploits around the MS KB I know that strangers aren't supposed to submit articles; only MS employees and contractors do. So I'm looking for a MS-affiliated sponsor who'd submit the article on my behalf. The credit does not matter; articles are anonymous anyway.
Full write-up here: http://social.msdn.microsoft.com/Forums/en/windowssecurity/thread/11b08625-b432-4667-ab82-a7e0ed008fc3
To open a support request, click "Support" from the primary navigation ribbon and then click the “Open a support request" button at the top of the page. Start by completing the New Support Request form. Select your product and describe the issue. Describe the severity of the issue and level of support required.
Contact Microsoft Store Support877-642-0419. Technical support.
It's typically over 2 weeks to get a technician and then when you do, responses are days apart. If it's a moderately difficult issue, the ticket will end up getting dropped.
Try submitting the relevant comments, writeup, etc. via the "Send comments about this topic to Microsoft" link from a top-level CryptoAPI MSDN page (which just generates an email).
EDIT: If you're a TechNet subscriber, you have two free incidents you can use to contact Microsoft about this. You'll also get guaranteed forum replies from Microsoft with a subscription. If you don't subscribe, you can pay some money for a one-time incident. Or, if you can phrase it as a Vista SP1 issue, you might be able to get some attention for free.
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With