gpg 1.0.6 tries to encrypt to wrong subkey

[disastry at saiknes.lv]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: RIPEMD160

gpg can't encrypt to key 0x587CA0C2:

E:\>echo a | gpg -r 0x587CA0C2 -ae
gpg: key 2DE0F7D0.391: created in future (time warp or clock problem)
gpg: 0x587CA0C2: error checking key: timestamp conflict
gpg: [stdin]: encryption failed: timestamp conflict

key have 3 subkeys - B31418BF expired, F21BD315 valid, and 2DE0F7D0 created in future:

E:>gpg -kv 0x587CA0C2
pub  1024D/587CA0C2 2000-12-31 Senshi Remailer <senshiremailer at gmx.de>
sub  2048g/B31418BF 2000-12-30 [expires: 2001-06-29]
sub  2048g/F21BD315 2001-06-15 [expires: 2001-12-30]
sub  2048g/2DE0F7D0 2001-12-15 [expires: 2002-06-29]

probably gpg tries to encrypt to wrong subkey :-/
I think it's bug.

(I know about --ignore-time-conflict,
I know that it's possible to select subkey this way 0xF21BD315!,
I know that problem will be no more after 2 deays)
__
Disastry  http://disastry.dhs.org/
http://disastry.dhs.org/pgp <----PGP plugins for Netscape and MDaemon
 ^--GPG for Win32 (supports loadable modules and IDEA)
 ^----PGP 2.6.3ia-multi05 (supports IDEA, CAST5, BLOWFISH, TWOFISH,
      AES, 3DES ciphers and MD5, SHA1, RIPEMD160, SHA2 hashes)
-----BEGIN PGP SIGNATURE-----
Version: Netscape PGP half-Plugin 0.15 by Disastry / PGPsdk v1.7.1

iQA/AwUBPBjRezBaTVEuJQxkEQPVxgCfQMOuVQ97FVhEhCfzpbYAj7C+PJAAoLdI
pg8Y766ThsT0w0bxj/OgNNHH
=KtOw
-----END PGP SIGNATURE-----