-
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
Adding real multi-part operations #186
Comments
Pkcs11Interop strictly follows vanilla PKCS#11 standard and proposed interfaces are BouncyCastle specific so I cannot say I like proposed approach very much. If it is really needed I would rather expose PKCS#11 functions you are missing in HighLevelAPI:
With these new methods you should be able to easily implement BTW did you check whether your |
Thank you for your fast answer! I got your opinionn about BC, and agree with you. But I don't know any alternative to BC on C#. May be do you know? Any way, multi-part HighLevelAPI operations are not urgent changes: I can use low-level api for implementation. If pkcs#11 functions will be used by somebody, I've write you and we can add HighLevel Init/Update/Final functions. |
I'm also not aware of any alternatives to BouncyCastle. |
👍 With this it would be also easier to implement the |
Also tried integrate with ICryptoTransform api and encountered troubles because of lack init/update/final in high level api. |
@adcy this issue originally discussed signing with BouncyCasle with |
@jariq I tried to create implementation of |
up |
Hello,
I'm trying to add primitive classes to Bouncy Castle, which will implements pkcs#11 signature, encryption, digest and so on. For example, to add pkcs#11 signature, I have to implement ISigner interface, which requeres Update function.
The problem is that HighLevel API of PKCS11Interop doesn't allow to do this. What do you think about adding pkcs#11 classes (ISigner, IVerifier, IDigester, IEncryptor, IDecryptor and so on), which allow real multi-part operaion support?
Usage of them may be similar to this:
What do you think about this interface? I can help you with implementation.
The text was updated successfully, but these errors were encountered: