May 2008 - Posts
Hi all, If you read CryptAcquireContext documentation, you'll see that setting pszContainer to NULL allow us to use a default key container . Microsoft recommends that every application creates its own key container instead of the default one, because
Read More...
Hi all, When we try to access a key container, CryptAcquireContext may return NTE_BAD_KEYSET (or error # 0x80090016 or -2146893802 or "Keyset does not exist") for the following two reasons: 1) key container doesn't exist . You may repeat the call to CryptAcquireContext,
Read More...
Hi all, welcome back, The following .NET 2.0 sample shows how to get security info from a folder to find out the permissions for users/groups on it: using System; using System.IO; using System.Security.AccessControl; using System.Security.Principal; namespace
Read More...
Hi all, welcome back, CryptAcquireContext API will fail with error #2 or ERROR_FILE_NOT_FOUND if: 1) the user's profile is not loaded, as we saw in my post RSACryptoServiceProvider fails when used with ASP.NET . 2) AppData registry value in the following
Read More...
Hi all, welcome back, I recently had a customer who needed to retrieve extensions from certificates the easy way in .NET 1.1 , and they wanted to use CAPICOM for that. In .NET 2.0 and later we may use X509Certificate2 to achieve the same results (I strongly
Read More...
Hi all, welcome back, As we read in Windows Security Center – Managing the State of Security , the vast majority of antivirus Independent Software Vendors (ISVs) support WMI integration. Windows Security Center uses it to detect antivirus and firewall
Read More...
