-
Notifications
You must be signed in to change notification settings - Fork 86
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
Expose LowLevelPkcs11Library from session #191
Comments
Such feature was present in Pkcs11Interop 4 but turned out to be problematic for quite a few reasons I don't recall right now. The preferred way to do this kind of stuff (calling low level methods not exposed by HighLevelAPI interfaces) in Pkcs11Interop 5 is to create your own set of extended classes inherited from Pkcs11Interop classes. For a working example please take a look at Pkcs11Interop.Mock project and |
I understand that concept. However this is only possible when you have the whole code path (factories etc.) under your control. Unfortunately this is not my case, since as a library author I need to work with an |
I don't understand why can't you work with "your" |
Because I'm not the one in charge of creating the session. I need to work with whatever |
Today we try to use the high level API for everything, however there are some scenarios not covered by the high level API (e.g. multi-part operations, #186). For this one must use the low level API. However there seems no easy way to transition from the high level to the low level in spite of the high level API is naturaly built on top of the low level.
I propose exposing the
LowLevelPkcs11Library
from theISession
so one could use if needed the following construct
The text was updated successfully, but these errors were encountered: