Skip to content
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

Closed
johann-pfefferl opened this issue Jan 5, 2022 · 2 comments · Fixed by #150
Closed

Two constants no longer exit #149

johann-pfefferl opened this issue Jan 5, 2022 · 2 comments · Fixed by #150

Comments

@johann-pfefferl
Copy link

When I upgrade my project to the newest release I get the following error

github.com/ThalesIgnite/crypto11
# github.com/ThalesIgnite/crypto11
../../../pkg/mod/github.com/!thales!ignite/crypto11@v1.2.5/crypto11.go:356:25: undefined: pkcs11.CK_EFFECTIVELY_INFINITE
../../../pkg/mod/github.com/!thales!ignite/crypto11@v1.2.5/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.

@miekg
Copy link
Owner

miekg commented Jan 5, 2022 via email

@miekg
Copy link
Owner

miekg commented Jan 5, 2022 via email

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 miekg closed this as completed in #150 Jan 5, 2022
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
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants