-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 31/07/12 1:14 AM, David Shaw wrote:
Yes, this is expected behavior. It follows from what I explained
earlier in this thread. When you use --override-session-key, you
bypass the quick check (after all, you gave the override key -
what is
While playing around with --override-session key , have noticed
that gpg gives many different sets of error messages when trying
out different session keys.
Here is an interesting example:
First, the gnupg encrypted text:
-BEGIN PGP MESSAGE-
Version: GnuPG v1.4.12 (MingW32)
Comment:
On Jul 30, 2012, at 10:45 AM, ved...@nym.hush.com wrote:
While playing around with --override-session key , have noticed
that gpg gives many different sets of error messages when trying
out different session keys.
[examples]
Borh examples give error messages identical to the first one,
On Mon, Jul 30, 2012 at 10:45 AM, ved...@nym.hush.com wrote:
While playing around with --override-session key , have noticed
that gpg gives many different sets of error messages when trying
out different session keys.
... CUT ...
Borh examples give error messages identical to the first one,
