-
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
Two constants no longer exit #149
Comments
[ Quoting ***@***.***> in "[miekg/pkcs11] Two constants no lon..." ]
When I upgrade my project to the newest release I get the following error
github.com/ThalesIgnite/crypto11
# github.com/ThalesIgnite/crypto11
***@***.***/crypto11.go:356:25: undefined: pkcs11.CK_EFFECTIVELY_INFINITE
***@***.***/crypto11.go:356:79: undefined: pkcs11.CK_UNAVAILABLE_INFORMATION
I don't know if this is a problem of the crypto11 package or the pkcs11.
I've reparsed everything from pkcs11t.h in #147, either I made a mistake there or these
constants don't exit in the spec
|
[ Quoting ***@***.***> in "[miekg/pkcs11] Two constants no lon..." ]
When I upgrade my project to the newest release I get the following error
github.com/ThalesIgnite/crypto11
# github.com/ThalesIgnite/crypto11
***@***.***/crypto11.go:356:25: undefined: pkcs11.CK_EFFECTIVELY_INFINITE
***@***.***/crypto11.go:356:79: undefined: pkcs11.CK_UNAVAILABLE_INFORMATION
I don't know if this is a problem of the crypto11 package or the pkcs11.
yep I know, i filter CK_ prefixes, because a lot of them looks off, apparently not. Should
be a quick fix.
|
miekg
added a commit
that referenced
this issue
Jan 5, 2022
Amend const_generate.go to not skip CK_* constants and have them in zconst.go as well. Special case (~0) for CK_UNAVAILABLE_INFORMATION. Fixes #149 Signed-off-by: Miek Gieben <miek@miek.nl>
miekg
added a commit
that referenced
this issue
Jan 5, 2022
Amend const_generate.go to not skip CK_* constants and have them in zconst.go as well. Special case (~0) for CK_UNAVAILABLE_INFORMATION. Fixes #149 Signed-off-by: Miek Gieben <miek@miek.nl>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When I upgrade my project to the newest release I get the following error
I don't know if this is a problem of the crypto11 package or the pkcs11.
The text was updated successfully, but these errors were encountered: