Exporting a CA Generated with ECC Keys

[aaalongueira]

Hello everyone,

I am trying to export a CA to obtain the P12 file cointaining its private key. This CA uses the ECC keys generated in a Crypto Token that is configured to allow the export of private keys.

I am following the instructions provided in the EJBCA Documentation. But when I click on the "Export CA keystore..." button, y get the error:

Key encryption key must be set to RSA key to allow key export.

Nevertheless, when I triedthe same test with a CA that uses an RSA Crypto Token, the export operation is performed without any issue.

Does this mean that only CAs using RSA keys can be exported?

[primetomas]

What you have to ensure is that your "keyEncryptKey" of the CA is an RSA key. I believe that's what it's complaining about. It's not about the CAs signing key. Are you using key recovery?

[aaalongueira]

Hello, Tomas!

I was not aware of the "Key Recovery" option in EJBCA.

On the other hand, all the keys in the CA are ECC:

• defaultKey
• certSignKey
• crlSignKey
• keyEncryptKey
• testKey

Does this mean that I cannot export this CA because the "keyEncryptKey" is not RSA? What is the reason behind such behaviour?

Thank you in advance!

[primetomas]

https://docs.keyfactor.com/ejbca/latest/key-recovery

Key recovery is an encryption operation and EC keys can not be used for encryption. If you read the documentation there there is possibility today to use EC keys as keyRecovery key. But this is likely going away due to the inconsistent and shaky behavior of EC key derivation on different brands of HSMs. If you are not aware of key recovery, you are not using it, and you can just put an RSA key there to "make it work". That key will not be used.

[primetomas]

In a not too distant future keyRecovery keys will move to use post-quantum cryptography. When HSMs and the eco-system are a bit more ready.