Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

CA Backup -> Private key is NOT exportable

2,189 views
Skip to first unread message

Juan

unread,
Jan 16, 2009, 11:55:01 AM1/16/09
to
Hi,


at the moment I'm testing Backup of a W2K8 CA. I used certutil to backup the
key using the following syntax:

certutil -f -backupkey C:\CertBackup

I only get one file. With certutil filename I got message that "Private key
is NOT exportable".

How can I change this behavour?

Many thanks in advance


Juan


Brian Komar (MVP)

unread,
Jan 18, 2009, 12:15:52 PM1/18/09
to
How did you generate the CA certificate? By default, a software-based CSP
will store the certificate in an exportable format on the machine.
1) Are you using an HSM? For an HSM, yuou cannot use certutil -backupkey,
you have to backup based on the HSM that you have using their native
routines or file system copy.
2) Did you import the certificate from a PKCS#12. If so, you had to enable
the private key export option at the time of import.
Brian

"Juan" <Ju...@discussions.microsoft.com> wrote in message
news:43EFB02C-3897-43F2...@microsoft.com...

Mounir IDRASSI

unread,
Jan 18, 2009, 12:46:01 PM1/18/09
to
Hi,

If your private key/certificate were created using a Microsoft CSP, you can
use the free tool JailBreak from iSEC : it will help you export certificates
and key pairs even if they were marked as "Not Exportable" upon their
creation. You can get it from the following link :

http://www.isecpartners.com/jailbreak.html

I have tested it and it works like a charm...

Cheers,
--
Mounir IDRASSI
IDRIX
http://www.idrix.fr

To reach me: mounir_idrix_fr (replace the underscores with the at and dot
characters respectively)

Brian Komar (MVP)

unread,
Jan 18, 2009, 8:07:32 PM1/18/09
to
Nice tool!
I guess this is another reason that I recommend HSMs for private key
protection. You just cannot secure a software-based machine key
Brian

"Mounir IDRASSI" <moon...@newsgroups.nospam> wrote in message
news:BD679D02-5929-4EA6...@microsoft.com...

0 new messages