Noah Misch 85270ac7a2 pgcrypto: Report errant decryption as "Wrong key or corrupt data". ... This has been the predominant outcome. When the output of decrypting with a wrong key coincidentally resembled an OpenPGP packet header, pgcrypto could instead report "Corrupt data", "Not text data" or "Unsupported compression algorithm". The distinct "Corrupt data" message added no value. The latter two error messages misled when the decrypted payload also exhibited fundamental integrity problems. Worse, error message variance in other systems has enabled cryptologic attacks; see RFC 4880 section "14. Security Considerations". Whether these pgcrypto behaviors are likewise exploitable is unknown. In passing, document that pgcrypto does not resist side-channel attacks. Back-patch to 9.0 (all supported versions). Security: CVE-2015-3167		2015-05-18 10:02:31 -04:00
..
3des.out
blowfish.out
cast5.out
crypt-blowfish.out
crypt-des.out
crypt-md5.out
crypt-xdes.out
des.out
hmac-md5.out
hmac-sha1.out
init.out
md5.out
pgp-armor.out
pgp-compression.out
pgp-decrypt.out	pgcrypto: Report errant decryption as "Wrong key or corrupt data".	2015-05-18 10:02:31 -04:00
pgp-encrypt-DISABLED.out
pgp-encrypt.out
pgp-info.out	Fix buffer overrun after incomplete read in pullf_read_max().	2015-02-02 10:00:45 -05:00
pgp-pubkey-decrypt.out	pgcrypto: Report errant decryption as "Wrong key or corrupt data".	2015-05-18 10:02:31 -04:00
pgp-pubkey-DISABLED.out
pgp-pubkey-encrypt.out
pgp-zlib-DISABLED.out
rijndael.out
sha1.out
sha2.out