Alexander Paetzelt
Alexander Paetzelt
Still get the message, any idea? Did it work on your side?
The support for OpenPGP Card v3 is mostly included already in OpenSC 19.0. I don't know how the implementation is working if you want to include it in a project...
> My question is, how can I "use" / call / link against the OpenSC/src/libopensc/card-openpgp.c and OpenSC/src/pkcs15-init/pkcs15-openpgp.c functions? As far as I can say you don't use them directly anyway....
> For a quick test, I use the pkcs11-tool (because this tool uses opensc-pkcs11.so) and I try to use sign with the ./pkcs11-tool -s --input-file ~/tmp/test.txt --output-file ~/tmp/test.sig Please try...
I realized the following: When importing a key-cert pair (aka a .p12 file) with `pkcs15-init --delete-objects privkey,pubkey --id 1 --store-private-key key-cert.pfx --format pkcs12 --auth-id 3 --verify-pin` the store is iterated...
I scratched my head and found the solution of the puzzle... I used a S/MIME cert-key pair of Commodo that I created in the past. In it are two more...
Please check my latest comment in code, this PR is breaking stuff otherwise imho.
@daringer I would suggest to follow Jakubs advice then and fix the overflow and only import the first cert. I can not think of a really good use case where...
This is already working with OpenSC and GnuPG. The only downside is that you can not (at least easily) use slot 3 (authenticate) for GnuPG stuff. But OpenSC can nearly...
actually, I think this ticket can be closed