NewPG is now GnuPG 1.9

[Simon Josefsson]

Compiles fine now, thanks.  However, when I try to sign something, it
selects an expired key.

$ mv .gnupg .gnupg-v1
$ rm -rf .gnupg
$ gpg
...
^D
$ cp .gnupg-v1/secring.gpg .gnupg-v1/pubring.gpg .gnupg
$ gpg2 -b -a
Secure memory is not locked into core
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!
 
You need a passphrase to unlock the secret key for
user: "Simon Josefsson <jas at nada.kth.se>"
1024-bit DSA key, ID 5C980097, created 2001-04-10
 
gpg: gpg-agent is not available in this session
foo
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.9.1-cvs (GNU/Linux)
 
iD8DBQA/MOdZ8U/viFyYAJcRAlJ5AKDT0lZHS7h0ccLKEi0sQNA9xzLlCACg4Mr3
Klo0rGd7XcpOGd3qUw80QJI=
=kg3x
-----END PGP SIGNATURE-----
$

The key selected expired long time ago:

pub   1024D/5C980097 2001-04-10 Simon Josefsson <jas at nada.kth.se>
uid                             Simon Josefsson <simon at josefsson.org>
uid                             Simon Josefsson <jas at extundo.com>
uid                             Simon Josefsson <jas at pdc.kth.se>
sub    768g/368A26A6 2001-04-10 [expires: 2002-04-10]
                                                                                
Perhaps this isn't a new problem though (gpg 1.3 behave the same), but
it would be nice to have GnuPG prefer a valid key, when available.

However, when I try to use my current key, it doesn't work:

$ gpg2 -b -a --default-key B565716F
Secure memory is not locked into core
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!
 
You need a passphrase to unlock the secret key for
user: "Simon Josefsson <jas at extundo.com>"
1280-bit RSA key, ID B565716F, created 2002-05-05
 
gpg: gpg-agent is not available in this session
foo
gpg: signing failed: Invalid public key algorithm
gpg: signing failed: Invalid public key algorithm
$

Old GnuPG work fine:

$ gpg -b -a --default-key B565716F
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: WARNING: using insecure memory!
gpg: please see http://www.gnupg.org/faq.html for more information
 
You need a passphrase to unlock the secret key for
user: "Simon Josefsson <jas at extundo.com>"
1280-bit RSA key, ID B565716F, created 2002-05-05
 
foo
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.3.2-cvs (GNU/Linux)
 
iQC1AwUAPzDn5e2iHpS1ZXFvAQKnFQT/Tt+ws4XisVsFlYmpbjQmTZp7zRvP0KBf
M2jAvIxv9oKXgbGhN2jUeVRNR7y+phXdv1hBcZ1hDkeF0WUI2ONqNIKeu/s0N9Nc
/bKnLTgnMZD/grKgF7NuAPRokO9OQM80LqI6QNiZNqqZFIeRDFDi5SYqz3mGvYsi
7Hl8NipQW7IL6edj5rws+I26q4VGN7r/KUcOncwqXDQUBqTh56wrNw==
=gjuh
-----END PGP SIGNATURE-----
jas at latte:~$

Here's the key:

pub   1280R/B565716F 2002-05-05 Simon Josefsson <jas at extundo.com>
uid                             Simon Josefsson <simon at josefsson.org>
sub   1280R/4D5D40AE 2002-05-05 [expires: 2003-11-06]
 
Any ideas?