In the previous lecture it said that the private key needed to be wrapped with a symmetric key before downloading. Doesn’t that mean that you need to decrypt the private key with your wrapping key before you can use it at all?
Might going out on a limb but I believe the wrapper key is for encrypting your keys for storage and replicating them across the cluster in this case. It is also probably used to store the key information in the HSM database while maintaining no knowledge of the key material. This was my guess with the CMK wrapper. It prevents Amazon from knowing the exact details of your private key so they can’t use it. So if your key gets compromised during HSM cluster replication via MITM attack, it should still be without having the wrapper key. Plus using a symmetric cipher is faster to decrypt for retrieval.
You are right, you have to decrypt the key before you use it. It is done with this command from the lab:
-out myprivatekey -w
The "myprivatekey" is decrypted and ready to use.
Application integration with HSM is a great way for PKI security and SSL offloading:
Removes the security risk of have multiple copies of a SSL private key on multiple devices. One of my dreams usage if I owned a HSM 🙂
I was confused by this too! This section of the documentation seems to explain it:
The exSymKey command writes a plaintext (unencrypted) copy of the secret key to a file. The export process requires a wrapping key, but the key in the file is not a wrapped key. To export a wrapped (encrypted) copy of a key, use the wrapKey command.
I can’t find documentation online for the
exportPrivateKey command but I assume it follows a similar process.