I have a very strange situation where the gpg command will fail to
verify whether there is valid PGP data in some files. Decrypting
these files works flawlessly. Here is an example:
[root@server autoimport]# gpg -vv --verify-files 01UserEnumswValues.txt.asc.txt
gpg: armor: BEGIN PGP MESSAGE
gpg: armor header: Version: GnuPG v1.4.7 (MingW32)
:pubkey enc packet: version 3, algo 16, keyid F0682D87CF4ED243
data: [1022 bits]
data: [1024 bits]
[root@server autoimport]# gpg -vv --verify-files 03users.txt.asc.txt
gpg: armor: BEGIN PGP MESSAGE
gpg: armor header: Version: GnuPG v1.4.7 (MingW32)
:pubkey enc packet: version 3, algo 16, keyid F0682D87CF4ED243
data: [1021 bits]
data: [1023 bits]
gpg: no valid OpenPGP data found.
Note that the first file is correctly identified as OpenPGP encrypted
data, and has exit status of 0.
The second file gives the error "no valid OpenPGP data found", even
though I'm able to decrypt the file with no problems. Both these
files were encrypted with the same key, and both contain plain text
CSV data.
Any ideas why this is failing on some files and not others?
_______________________________________________
CentOS mailing list
CentOS@xxxxxxxxxx
http://lists.centos.org/mailman/listinfo/centos
