-
Notifications
You must be signed in to change notification settings - Fork 88
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
V1 rewrite #40
V1 rewrite #40
Conversation
Changing to the config I use with SoftHSM. Still won't suit most people, but neither did the original.
Apologies for massive commit, but rather difficult to split a wholesale change into small parts. Many aspects are yet to be done, including changing id/label behaviour, adding attributes, adding cert support, etc. Completely untested; tests expected to fail.
Fixes #37.
Accidentally muddled two commits on different topics.
We can no longer test this, as we update the source code
This commit also addresses an issue where errors during Configure resulting in the PKCS#11 library remaining initialized. Now all error paths kill the library.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just a single small change from a quick scan.
I've pushed a few more changes. Mostly about removing errors from our API. However, I decided to adjust the find keys stuff so it returns nil if the keys aren't found, not an error. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
The tag for this release is |
Thanks @cbroglie, I've just corrected that. |
Re-write of crypto11 to implement various backwards-incompatible design changes. This PR will be released as v1.0.0, beginning a new commitment to API stability.
Many of the topics in #36 are addressed, plus several outstanding issues:
The main thing discussed in #36 that wasn't implement was the
WithAttributes
functions. I'm not sure they are needed, so I'm happy to wait for someone to request them. I'll create an issue to capture that as a potential enhancement. There is a branch,with-attributes
, the contains the beginning of some work on this. #20 also hasn't been implemented, but it will be.