Your question is a bit hard to answer.

Generally a wrapped key can be unwrapped outside the HSM. You should use the same cryptographic algorithm you used to wrap.

You should load in the HSM a wrapping key (for example a 3DES key) by using CreateObject. Then you can generate a key pair specifying in the tamplate CKA_EXTRACTABLE = TRUE. This flag allows to make the key pair wrappable (if the HSM allows wrapping on the private keys). Than, you can extract the key pair by calling WrapKey specifying as the wrapping key the 3DES key above. Finally, on the other side, without the HSM, you must write a piece of code that implements the wrapping cryptographic algorithm and call your code by using the wrapping key to unwrap the wrapped key.

Note about WrapKey function (as stated in the PKCS#11 specification):

C_WrapKey can be used in the following situations:
• To wrap any secret key with a public key that supports encryption and decryption.
• To wrap any secret key with any other secret key. Consideration must be given to key
size and mechanism strength or the token may not allow the operation.
• To wrap a private key with any secret key.

Regards,

Ugo Chirico

It's not exactly true.

When you call Wrap method you get the encrypted wrapped key in form of array of bytes, not merely as an object reference. When you call the Wrap method you get the byte array containing the encrypted (wrapped) key. Then, you can do what you want with that encrypted key. To store it in another system you have to decrypt it and you can do decryption if you know the secret key used to encrypt (wrap) the other key (you surely know the algo because when you call Wrap you have specified the mechanism).

To reach your goal simply you should use your own key to wrap the other key and you should use an implementation of the wrapping algorithm to decrypt (unwrap) it.

If you really need that and you don't know ho to do I can develop for you the classes you need.

This is the snippet that loads a DES secret key:

// your wrapping key
byte[] keyValue = {0x11,0x12,0x13, 0x14, 0x15,0x16,0x17,0x18};

CryptokiCollection template = new CryptokiCollection();
template.Add(new ObjectAttribute(ObjectAttribute.CKA_CLASS, CryptokiObject.CKO_SECRET_KEY));
template.Add(new ObjectAttribute(ObjectAttribute.CKA_KEY_TYPE, Key.CKK_DES));
template.Add(new ObjectAttribute(ObjectAttribute.CKA_ID, id));
template.Add(new ObjectAttribute(ObjectAttribute.CKA_LABEL, label));
template.Add(new ObjectAttribute(ObjectAttribute.CKA_TOKEN, true));                
template.Add(new ObjectAttribute(ObjectAttribute.CKA_VALYE, keyValue));
template.Add(new ObjectAttribute(ObjectAttribute.CKA_PRIVATE, true));
template.Add(new ObjectAttribute(ObjectAttribute.CKA_MODIFIABLE, false));

CryptokiObject deskey = CurrentSession.Objects.Create(template);

Regards, 

Ugo

No. Using GenerateKey you are asking to the HSM to generate a new key so you cannot set the key value.

The only way to set the key value is by using CreateObject as I explained before.

Error 113 (wrapping key handle invalid) doesn't mean that you cannot wrap a key with a DES key.

How do you create the DES key? and the key to wrap?

Please read carefully the PKCS#11 specification. I have think that you need to understand better the PKCS#11 specs:

http://wiki.ncryptoki.com/GetFile.aspx?File=%2fdocs%2fpkcs-11v2-20.pdf

This depends on the underlying PKCS#11 module. PKCS#11 spec says nothing about the internal format of a wrapped key and NCryptoki does nothing on the format. It simply forwards what the underlying PKCS#11 module returns.

To see the exact format you should decrypt by yourself the wrapped key externally, without using a PKCS#11 module.

Don't worry about the topic. it may interest other developers.

The byte array you got is the plaintext (decrypted) of the wrapped key. What is the type of the wrapped key? RSA, ECC or something else?

Usually, in the most of PKCS#11 modules, a wrapped key is in ASN.1 DER encoding. to check that open you key in an hex editor and check whether it starts with 0x30 0x81 0xXX ... if so it is ASN.1 DER encoding.

The usual format for RSA and some other keys is defined in PKCS#n specifications (PKCS#12 for RSA key pairs, and so on)

Very good.

it is DER format of PKCS#8: http://www.rsa.com/rsalabs/node.asp?id=2130