HSM Vendor configurations about xipki HOT 5 CLOSED

Adding new constant is not possible. You can only override the vendor constants defined in PKCS11Constants.java.
Taking CKK_VENDOR_SM2 as example, it specifies the constant value to the SM2 key type. Since SM2 key type is not specified in the PKCS#11 standard, each HSM vendor may use different constant value. In the java code, I assign CKM_VENDOR_SM2 = 0xFFFFF001L (see https://github.com/xipki/jpkcs11wrapper/blob/main/src/main/java/org/xipki/pkcs11/wrapper/PKCS11Constants.java#L1240). In the vendor.conf you may override this with the value defined by the HSM vendor.

BTW: It is better to have an issue under the project xipki/jpkcs11wrapper to discuss the usage of jpkcs11wrapper.

from xipki.

You can define your own vendor.conf and point it via the java property org.xipki.pkcs11.vendor.conf (-Dorg.xipki.pkcs11.vendor.conf=/path/to/your/vendor.conf-file).

BTW: Do you use jpkcs11wrapper in xipki or your own project? Please update to latest version (v1.0.4).

from xipki.

Hi,

Yes, I'm currently upgrading the jpkcs11wrapper version from 1.0.1 that I was using, to 1.0.4 which is very helpful on managing sessions on it's own .

Can you give me an brief explanation about VENDOR_BEHAVIORS? I can't really understand how it works! And I can't customize the name for example from CKK_VENDOR_SM2 to CKK_SOMETHING_SM2?

Really appreciate the help!

from xipki.

Hi,

Sorry, didn't notice that I created the issue in the root of the repositories, my bad!

Thank you for all the information, now I know how to configure those mechanisms.

from xipki.

Please also take a look at xipki/ipkcs11wrapper. It supports more algorithms.

from xipki.