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

Add an example for dealing with DATA objects to the readme #58

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

h3po
Copy link
Contributor

@h3po h3po commented Jun 3, 2019

Just a proposal; I guess you might want to keep the documentation focused on dealing with public key crypto. Maybe it's time to make an example directory for the more obscure example scripts?
I don't see a straightforward way to add tests for this, as I don't own any of the devices that you are targeting. It'll be a while before I can test with a standard card or token.
This ObjectClass.DATA stuff is coming from me because I'm in the progress of writing a fuse fs driver capable of mounting a pkcs11 smartcard with the goal of storing zfs disk encryption keys on there.

@danni Just a proposal, I guess you might want to keep the documentation focused on dealing with public key crypto. I am developing with a proprietary pkcs11 library on a token with a proprietary pkcs15 applet, so I'd be happy if you could test this with your nitrokey or other opensc compatible token. It'll be a while before I can test with a standard card or token. This ObjectClass.DATA stuff is coming from me because I'm in the progress of writing a fuse fs driver capable of mounting a pkcs11 token with the goal of storing zfs disk encryption keys on there.
@danni
Copy link
Collaborator

danni commented Jun 4, 2019

I don't think I'd add this to the documentation, but it could be added to a test, even if that targets only your pkcs#11 implementation.

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 this pull request may close these issues.

2 participants