Unusual (unintended?) behavor upon decryption of a message // follow-up correction

2013-11-19 Thread vedaal
vedaal at nym.hush.com vedaal at nym.hush.com wrote onTue Nov 19 18:14:31 CET 2013 : >gpg: public key decryption failed: bad passphrase >gpg: encrypted with unknown algorithm 163 >gpg: decryption failed: unknown cipher algorithm >(the passphrase used was: 12345) >Now here is the last part of th

Unusual (unintended?) behavor upon decryption of a message // follow-up correction

2013-11-19 Thread vedaal
>If the message is encrypted to one public key, and also encrypted >symmetrically instead of to a second public key, then the symmetric algorithm >used by gnupg is the >same for the encryption of the session key to the public >key, as well as the session key to the symmetrically encrypted part,

Re: Unusual (unintended?) behavor upon decryption of a message // follow-up correction

2013-11-19 Thread Peter Lebbing
On 19/11/13 20:47, ved...@nym.hush.com wrote: > This is still unusual, as gnupg already identified it as TWOFISH, not as an > unknown algorithm, TWOFISH was used to encrypt the session key. What was used to encrypt the data is still unknown, since that knowledge is encrypted. (With TWOFISH. Are y