OK, I'm getting frustrated with the interaction with the smart card.
I have generated a new ElGamal encryption key, 0x16AF3873.
$ gpg --edit-key 51192ff2
gpg: NOTE: THIS IS A DEVELOPMENT VERSION!
gpg: It is only intended for test purposes and should NOT be
gpg: used in a production environment or with production keys!
Secret key is available.
pub 1024D/51192FF2 created: 2002-03-22 expires: never usage: CS
trust: ultimate validity: ultimate
sub 2048g/1DA6A1C7 created: 2003-06-27 expired: 2004-06-26 usage: E
sub 2048g/9150664F created: 2004-07-01 expired: 2005-07-01 usage: E
sub 2048g/96FAE64B created: 2002-03-22 expired: 2003-04-16 usage: E
sub 2048g/0193A5EB created: 2003-04-15 expired: 2004-04-14 usage: E
sub 2048g/16AF3873 created: 2005-08-10 expires: 2006-08-10 usage: E
sub 1024R/4A1C1224 created: 2005-06-27 expires: never usage: S
sub 1024R/F40CACBA created: 2005-06-27 expires: never usage: E
sub 1024R/694C9CA5 created: 2005-06-27 expires: never usage: A
OK, so I have exactly one valid signing key available on this machine
(RSA 4A1c1224, which is on a smart card), as evidence:
$ gpg --list-secret-keys
gpg: NOTE: THIS IS A DEVELOPMENT VERSION!
gpg: It is only intended for test purposes and should NOT be
gpg: used in a production environment or with production keys!
/home/amauer/.gnupg/secring.gpg
-------------------------------
sec# 1024D/51192FF2 2002-03-22
ssb 2048g/1DA6A1C7 2003-06-27
ssb 2048g/9150664F 2004-07-01
ssb 2048g/16AF3873 2005-08-10
sec# 1024D/51192FF2 2002-03-22
ssb# 2048g/1DA6A1C7 2003-06-27
ssb# 2048g/9150664F 2004-07-01
ssb# 2048g/96FAE64B 2002-03-22
ssb# 2048g/0193A5EB 2003-04-15
ssb# 2048g/17804FC1 2005-08-10
ssb# 2048g/16AF3873 2005-08-10
ssb> 1024R/4A1C1224 2005-06-27
ssb> 1024R/F40CACBA 2005-06-27
ssb> 1024R/694C9CA5 2005-06-27
ssb# 1024D/3F52F59F 2004-12-13
But, when I go to sign a file (or email, or anything) I get:
$ gpg --sign test.txt
gpg: NOTE: THIS IS A DEVELOPMENT VERSION!
gpg: It is only intended for test purposes and should NOT be
gpg: used in a production environment or with production keys!
gpg: secret key parts are not available
gpg: no default secret key: general error
gpg: signing failed: general error
What could be causing this?
Thanks
-Alex Mauer "hawke"
--
Bad - You get pulled over for doing 90 in a school zone and you're drunk
off your ass again at three in the afternoon.
Worse - The cop is drunk too, and he's a mean drunk.
FUCK! - A mean drunk that's actually a swarm of semi-sentient
flesh-eating beetles.
OpenPGP key id: 0x51192FF2 @ subkeys.pgp.net
_______________________________________________
Gnupg-users mailing list
Gnupg-users@gnupg.org
http://lists.gnupg.org/mailman/listinfo/gnupg-users
