Marking private keys as non-exportable with certutil -importpfxhttp://blogs.technet.com/pki/archive/2007/07/29/marking-private-keys-as-non-exportable-with-certutil-importpfx.aspxWhen importing a PFX-file with the certificate import wizard, you can choose if the private key should be exportable or not. Your choice is stored in the key storage property identifier that is key-storage specific. In other words, there is no informationen-USCommunityServer 2.1 SP1 (Build: 61025.2)Strong name signing in Visual Studio 2005 requires KeySpec=2 (AT_SIGNATURE)http://blogs.technet.com/pki/archive/2007/07/29/marking-private-keys-as-non-exportable-with-certutil-importpfx.aspx#2752158Thu, 17 Jan 2008 00:09:44 GMTd5e57398-b9ef-4490-9955-07cbb4e4a80d:2752158Andreas Klein<p>As noted in this article Visual Studio 2005 cannot handle PKCS#12 files that hold several certificates</p> Importing Multiple Certificateshttp://blogs.technet.com/pki/archive/2007/07/29/marking-private-keys-as-non-exportable-with-certutil-importpfx.aspx#2857258Sat, 09 Feb 2008 20:56:24 GMTd5e57398-b9ef-4490-9955-07cbb4e4a80d:2857258Colin Bowern<p>Through a recent migration we needed to move a large number of SSL certificates. After spending a lot</p>