-
Notifications
You must be signed in to change notification settings - Fork 134
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
use v3? #146
Comments
jeez the spec has published incorrect header files and they are fixing them here: https://github.com/oasis-tcs/pkcs11/tree/master/working/headers Grabbed oasis-tcs/pkcs11@188b0b1 |
Hey miekg, How long would it take for HSM Providers to offer v3 functionality do you think? months or years? Would there be breaking changes if using the updated v3 bindings with an HSM firmware that's still on 2.4 for example? Thanks |
[ Quoting ***@***.***> in "Re: [miekg/pkcs11] use v3? (Issue #..." ]
Would there be breaking changes if using the updated v3 bindings with an HSM
firmware that's still on 2.4 for example?
no idea, one would hope the pkcs11 folks thought about this. I note that this v3 branch
doesn't break the (few) tests we have in this repos... So works for me :-)
|
Prolly makes sense to upgrade to that version.
See http://docs.oasis-open.org/pkcs11/pkcs11-base/v3.0/pkcs11-base-v3.0.html
The text was updated successfully, but these errors were encountered: