Closed PlatinumDragon closed 4 years ago
Please send debug logs of the gnupg-pkcs11-scd.
On Tue, May 21, 2019 at 9:38 PM PlatinumDragon notifications@github.com wrote:
I'm trying to generate keys on Alladin eToken pro 64k using gpg --card-edit and I get Key generation failed: Bad session key gpg (GnuPG) 2.2.15 gnupg-pkcs11-scd 0.9.2
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/alonbl/gnupg-pkcs11-scd/issues/18?email_source=notifications&email_token=AAJURLLX3I2YUXU7HSBHGBLPWQ6SBA5CNFSM4HONVMO2YY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4GVBDQ4A, or mute the thread https://github.com/notifications/unsubscribe-auth/AAJURLKGPJONON3V376TJPTPWQ6SBANCNFSM4HONVMOQ .
Thanks! Please paste configuration.
log-file /home/admin/pkcs11log
verbose
providers p1
provider-p1-library /usr/lib/libeToken.so
openpgp-sign 799D38BE073EFB38CF38322F752740F13BD419C6
openpgp-encr 799D38BE073EFB38CF38322F752740F13BD419C6
openpgp-auth 799D38BE073EFB38CF38322F752740F13BD419C6
I believe you followed the gnupg-2.0 sequence while you have you have gnupg-2.1. Please follow the gnupg-2.1 sequence[1]
[1] https://github.com/alonbl/gnupg-pkcs11-scd/blob/master/gnupg-pkcs11-scd/gnupg-pkcs11-scd.1
I'm trying to generate keys on Alladin eToken pro 64k using gpg --card-edit and I get
Key generation failed: Bad session key
gpg (GnuPG) 2.2.15 gnupg-pkcs11-scd 0.9.2