-
Notifications
You must be signed in to change notification settings - Fork 47
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
Quirk: no-operation-state #324
Conversation
I think this looks good, but also think this option should be a quirk and not a full-fledged separate option. |
a8e045f
to
14ab66f
Compare
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.
Only minor nits on the docs text, otherwise LGTM
6d65ee0
to
bd18833
Compare
Configuration property to indicate whether the PKCS11 provider supports getting/setting the operation state. If it is not supported, no attempts will be made to duplicate the context. Signed-off-by: Florian Wernli <[email protected]>
de01045
to
2ae7363
Compare
Test for quirk no-operation-state. Signed-off-by: Florian Wernli <[email protected]>
2ae7363
to
2f260f4
Compare
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
Thanks, this looks good. |
Configuration property to indicate whether the PKCS11 provider supports getting/setting the operation state. If it is not supported, no attempts will be made to duplicate the context.
I already mentioned it in the discussion (#320) that the current approach leaves traces in the SSL error stack.
Please let me know what you think of this change.
(Tests will follow)