Mailing List Archive

GnuPG 2.0.19 + Cryptostick - decryption fails with 4096 bit key
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Hello,

I have recently generated subkeys to use with a GPF Cryptostick. I
decided to make full use of the ability to use 4096 bit keys with
recent versions of GnuPG ( > 2.0.18 I think). Everything is working
except when trying to decrypt a file or message encrypted to my
encryption subkey.

On this topic, I have found the following thread on the GPF forums,
which lead me back to this list.

https://www.privacyfoundation.de/forum/viewtopic.php?f=13&t=1145


The error output is the same as in the above thread, with no more
detail than:

gpg: public key decryption failed: General error
gpg: decryption failed: No secret key


Somehow, gpg2 is not able to read the key from the card. Is this a
known bug? I have not found anyone else documenting this.


Thanks,
Mat

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.19 (GNU/Linux)

iQIcBAEBCAAGBQJPzjcVAAoJEOb1qSIu+bHnmG4QAIJeqqLkRFhnVnONzFAW36MH
2uXisY/5jGLxaz/tiugFB57j4vOm9WJJ391iEa63quZDjuXnqW5UgKm94WZ7VmTb
RJ61B0laKfiOi57liOIYF6Sck83+AarkRy9ohiekyXlE36lQNWQq7rmeq0QUJ51l
qaGZkVTX6KFNc29s72EIU0AC7Sqa9649UTVRecfWqmd2HjH5apxS92cIpRphVQj0
r752jRpYR0VuRjwaAJicVeg1A3Vq+BsqptwkqcpGeTILR+6bnRDOxSs/MvpIEK/h
mg47BXIeRPMiO3LuWPw0TjfLVNtBet89BZqZ0VY/NVAWNI8n01B/HpGl8T8fApH1
8kfWVgLfinjg4ejlLC9NBz5pj7LI+GzVY+uUXpjLR0zsuCnT+WbsqAVCLmK36UDQ
ZN1PsjL/cnjBafyelAyTbe88dFd7PDzvPu0JaHHoyPz90WIfFSFLX9IwTGyGrW/8
rrGxUX0BFyg9hw1kFv4lzwss1tO6SGMrt3adNTt5fx9ZNJ1KAUaq7M03jSs9qEZ/
4W1dh7EzK3RFDUAbL5NaqcWVjc0KlAj64jUYGpWv7hvIQvZ8WKcIjvUdG98Blpsf
vC/d7xNDCc1hfDbcre0CkIueTuTP86+g8PGfURqz2rkz1oYEMe8tuKBKpNIaAxKQ
//+eIxetiaUvr8VlsTLa
=O7pO
-----END PGP SIGNATURE-----

_______________________________________________
Gnupg-users mailing list
Gnupg-users@gnupg.org
http://lists.gnupg.org/mailman/listinfo/gnupg-users
Re: GnuPG 2.0.19 + Cryptostick - decryption fails with 4096 bit key [ In reply to ]
On Tue, 5 Jun 2012 18:43, mat@spoked.ca said:

> Somehow, gpg2 is not able to read the key from the card. Is this a
> known bug? I have not found anyone else documenting this.

I don't have a crypto stick, thus I can't test it.


Shalom-Salam,

Werner

--
Die Gedanken sind frei. Ausnahmen regelt ein Bundesgesetz.


_______________________________________________
Gnupg-users mailing list
Gnupg-users@gnupg.org
http://lists.gnupg.org/mailman/listinfo/gnupg-users
Re: GnuPG 2.0.19 + Cryptostick - decryption fails with 4096 bit key [ In reply to ]
On Tue, Jun 5, 2012 at 6:43 PM, Mathieu Jolicoeur <mat@spoked.ca> wrote:
> On this topic, I have found the following thread on the GPF forums,
> which lead me back to this list.
>
> https://www.privacyfoundation.de/forum/viewtopic.php?f=13&t=1145

This could be pretty much the same issue which Edmond and Kevin are
experiencing:

http://lists.gnupg.org/pipermail/gnupg-users/2012-April/044195.html
http://lists.gnupg.org/pipermail/gnupg-users/2012-May/044335.html

_______________________________________________
Gnupg-users mailing list
Gnupg-users@gnupg.org
http://lists.gnupg.org/mailman/listinfo/gnupg-users
Re: GnuPG 2.0.19 + Cryptostick - decryption fails with 4096 bit key [ In reply to ]
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

On 06/05/2012 05:46 PM, Richard wrote:
>
> This could be pretty much the same issue which Edmond and Kevin
> are experiencing:
>
> http://lists.gnupg.org/pipermail/gnupg-users/2012-April/044195.html
>
>
http://lists.gnupg.org/pipermail/gnupg-users/2012-May/044335.html

Thanks for the references. After reading them, I come to the same
conclusion. I enabled the debug log for scdaemon and can attest to the
same behavior. There is no interaction with the card in the log when
trying to decrypt.

Mat
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.19 (GNU/Linux)

iQIcBAEBCAAGBQJPzojwAAoJEOb1qSIu+bHnanAP/RDPqsAQTsFyHNzQEZoz8Jnl
SWXiUy3bWiIxQC00fkZpRUU9I15WRAFYybqnhO1hzdNkhJ9u+Gq+JUq53tygBee3
dz5YeR9vOyyaPr9hGC9IvpqGVNH5fdvOGZGZ1x3S6k5PYtBi2BGlOS1nbtC9Kf/S
PNwO2Gme9QI8+xRCD8mMTcxnRlUjmBpR25exjFF1bnJklSB/ah59x7oHoE98o3iQ
EW2gJZEE9fi2Mqnbe11ObevcolBUqP0NUiS+dPLpn1hJUj3d7Eb6zlBhM12Eu+uA
SF871BkmAI6Bp0KtaritWaPUPBxmY+fMHvbYINhMu97G1gf3gq2Vsezj7Ddjq6tW
lzZKpZc1Uc9PT47pPz5zrieWrxR44YRIZpmAkXyGYrslEdNnH7jkrEwY5u5TlAs+
ETYmwBAmxfFTcejgSW8hh6NXzatGHDBb8p4M7FG3LU8zHEBYHzHamtTLyzo4h1c1
jw7+KxgGVyD2IQVnn9aPUy2fhZuPRF2zBBNA82hMWTlJFL8Ryv2J6iF2To2wXDS0
OcHTfTPU8f6xgXLniO60cy5v50RODBPY8C7Ymr2zdqSjSHWHWiVnOpDBOtTy5h+0
b0Mai+AZvC6enxOjZssCDsQmHbZ2Uv1o5dCWxOE+l4+7p7iJKXpeOxFMYwEXVZYh
Mfm/qzzQtlR1ACxc4BhQ
=ge8C
-----END PGP SIGNATURE-----

_______________________________________________
Gnupg-users mailing list
Gnupg-users@gnupg.org
http://lists.gnupg.org/mailman/listinfo/gnupg-users