On Tuesday, November 19, 2013 at 3:02 PM, "Peter Lebbing"
wrote:
>
>On 19/11/13 18:14, ved...@nym.hush.com wrote:
>> Why does gnupg give these types of error message, as opposed to
>simply
>> stating 'decryption failed: bad passphrase' ??
>>
>> What kind of relationship is there between the
>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,
On 19/11/13 22:37, ved...@nym.hush.com wrote:
> But this isn't the way hybrid gnupg messages work.
>
> Gnupg does not use one symmetric algorithm to encrypt the session key, and
> then another to encrypt the message. The user can choose 'which' symmetric
> algorithm to use, but it will be the same
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
On 19/11/13 18:14, ved...@nym.hush.com wrote:
> Why does gnupg give these types of error message, as opposed to simply
> stating 'decryption failed: bad passphrase' ??
>
> What kind of relationship is there between the number listed for the
> 'unknown algorithm' and the passphrase string that was
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
On Tuesday, November 19, 2013 at 3:51 AM, fuzzykitt...@riseup.net wrote:
>
>Upon decryption of the attached message, the program requests a new
>passphrase. Then after any arbitrary string is entered (or
>nothing),
>decryption of the message fails. It does not matter if any private
>keys
>are hel
On 19/11/13 10:15, Laurent Jumet wrote:
> In my opinion, this is a symetric crypted message. You need the exact
> password (called passphrase as well) to decrypt it, but it's not a double key
> cipher.
You're only partly correct. Letting 'gpg2 --list-packets --list-only' inspect
the message, I
Le 19/11/2013 08:28, fuzzykitt...@riseup.net a écrit :
Upon decryption of the attached message, the program requests a new
passphrase. Then after any arbitrary string is entered (or nothing),
decryption of the message fails. It does not matter if any private keys
are held in gnupg (including the
Upon decryption of the attached message, the program requests a new
passphrase. Then after any arbitrary string is entered (or nothing),
decryption of the message fails. It does not matter if any private keys
are held in gnupg (including the key of the intended recipient).
Here is the message in q
10 matches
Mail list logo
