Lack of backwards compatability?

[Alphax]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Some old versions of GPG (1.0.x?) had support for the TIGER192 hash, but
this was later removed when it was dropped/rejected from the OpenPGP
standard.

However, these versions of GPG (and possibly some versions of PGP as
well) are still able to produce signatures using the TIGER192 hash
algorithm, with no way to verify them in the current version of GPG.

Is it possible to add the capability to verify signatures made with this
hash? The fact that prior versions were able to create such signatures
but newer versions are not able to verify them really breaks backwards
compatability standards.

Thanks,
- --
Alphax                      |   /"\
Encrypted Email Preferred   |   \ /     ASCII Ribbon Campaign
OpenPGP key ID: 0xF874C613  |    X   Against HTML email & vCards
http://tinyurl.com/cc9up    |   / \
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (MingW32)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iQEVAwUBQ0pTD7MAAH8MeUlWAQjEkQf/RFoFJEeDSNOMrg3hEiI2Ge7REzQa8ZZ9
oK9alTSBWZ0dtkJxYs9c6lW6kGd0wW+b7TqVa4b2plpyYZwLxfHLypuuSyd3VnXP
ECg/xjxabBEUwZMo8hpREHzgkV9MxaJarLR1LMppqLjdQdd+06Bv6HogAKg3vzJN
2uBcwl6eBEZ0l3AScjZv92ZMmRwD1b9wTASmDYY/iKQJJotvjSZyey0eBmbiCJ7V
W1FggX+weNI7BKCWdofhNvlNjtDXBxpfc89i5+sduXNFlhm63FmmMpBRWziPpXJJ
2TA2TuKf6GB0eucVZtAaO9yE0ChphMwTDxg/oLOdOBdmTRYDieu5dw==
=tFKF
-----END PGP SIGNATURE-----