Bad key - decrypting armoured symmetric message

[lion at lion.leolix.org]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

reflum,

> GPG does not decrypt my armoured symmetric messages from STDIN it gives
> 'Bad key' error, but it decrypts the same message if supplied from a
> file, is there a problem here or a reason why I cannot input an armoured
> symmetric message on the STDIN and provide a password and get back
> cleartext?
> 
> It seems the erronous scenario does not have the extra :compressed
> packet and :literal data packet log messages, what significance this is
> I am not sure, any help would be appreciated.
> 
> See below for example (the passphrase is 'a' and the message 'Hello!'):
> 
> -----BEGIN PGP MESSAGE-----
> [...]
> -----END PGP MESSAGE-----
> 
> C:\data\work\docs>gpg -vva

$ gpg -vva
gpg: Go ahead and type your message ...
- -----BEGIN PGP MESSAGE-----
Version: GnuPG v1.4.2 (MingW32)

jA0EAwMCEBfNHm+FYa9gyR4qiZadhiuMYirc+ZtnmjrCx46gWBfcD3bWYl8cE+s=
=G4bz
- -----END PGP MESSAGE-----
gpg: armor: BEGIN PGP MESSAGE
gpg: armor header: Version: GnuPG v1.4.2 (MingW32)
:symkey enc packet: version 4, cipher 3, s2k 3, hash 2
        salt 1017cd1e6f8561af, count 96

gpg: CAST5 encrypted data
:encrypted data packet:
        length: 30
:compressed packet: algo=1
:literal data packet:
        mode b, created 1139537370, name="",
        raw data: 8 bytes
gpg: original file name=''
Hello!
gpg: decryption okay
gpg: WARNING: message was not integrity protected


for me it works perfect.
I think maybe is this a bug(?) depending on window$.
Windows have no TTY mengment like UNIX and gpg maybe can not handle
the pgp messege and the passphrase on the same filehandle under window$.

It tryed out your example on many of my systems an I _allways_ got
what I posted above.

- ---
Philipp.
  (Rah of PH2)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2 (NetBSD)

iD8DBQFD7dJlMjUtRWf3gmQRAm1eAJ4kJSGRgFA9hrDPD5NhWreL/fNGpgCeOYkG
iQbgMYMUksUHFKc3yKiJqjQ=
=hXpB
-----END PGP SIGNATURE-----