Open to non-standard PKCS11 Mechanisms?

[Hussainity]

Would this project accept "vendor specific" but somewhat common additions to PKCS11?

Specifically looking at algorithms that would enable key splitting, like CKM_XOR_BASE_AND_KEY which is not present in OASIS's spec but does exist in Thales's programming guide.

[Hussainity]

Here is my own use: https://github.com/Hussainity/SoftHSMv2/tree/hm/xor-base-and-key

[t-j-h]

This is not a good idea. We should not encourage vendor specific usage. Raise this with the pkcs11 technical committee or ask your Thales rep to do so and encourage a standard mechanism to be added if there is clear need for something and it is missing.

[Hussainity]

Acknowledged, will consider raising this with the TC.

[bukka]

I agree, we shouldn't be introducing non standard things. Also we don't want to diverge too much from p11-kit headers that we use for pkcs11.h with really minor tweaks so you would probably need to first ask them to add it...