with 1 passphrase
gpg: DBG: cleared passphrase cached with ID: S8E43B9269CCD3E30
gpg: decryption failed: Bad session key
if i use
amma@amma-Aspire-F5-571 ~/Desktop $ gpg -d mtogo.zip.gpg
gpg: CAST5 encrypted data
gpg: encrypted with 1 passphrase
gpg: decryption failed: Bad session key
same thing
phrase
gpg: decryption failed: Bad session key
Regards,
--
Frank Hrebabetzky +49 / 9261 / 950 0565
___
Gnupg-users mailing list
Gnupg-users@gnupg.org
http://lists.gnupg.org/mailman/listinfo/gnupg-users
tu 18)
Since then, A wasn't re-encrypted, and I can decrypt it as before. B
however was re-encrypted, and now I cannot decrypt it anymore. Each
attempt is responded with
gpg: AES256 encrypted data
gpg: encrypted with 1 passphrase
gpg: decryption failed: Bad session ke
Hi Frank,
On 03/01/2019 15:25, Frank Hrebabetzky wrote:
> gpg: AES256 encrypted data
> gpg: encrypted with 1 passphrase
> gpg: decryption failed: Bad session key
This is also the error message you get when you specify the wrong
passphrase. Perhaps you mistyped the passphrase when encr
On 1/20/19 5:34 PM, Peter Lebbing wrote:
Hi Frank,
On 03/01/2019 15:25, Frank Hrebabetzky wrote:
gpg: AES256 encrypted data
gpg: encrypted with 1 passphrase
gpg: decryption failed: Bad session key
This is also the error message you get when you specify the wrong
passphrase. Perhaps you
s due to the mechanics of
symmetrically-encrypted OpenPGP messages. The passphrase is used to
decrypt the session key. A wrong passphrase just results in garbage on
decryption. This garbage then leads to the "Bad session key" message.
I wrote some stuff about possible changed handling of
