I've used the patch in the stable 2.0 branch to create a patch for the
1.4 series. We might apply it after the wheezy release.
Regards, Daniel
--- a/g10/keylist.c
+++ b/g10/keylist.c
@@ -1370,19 +1370,15 @@
print_string( stdout, p, n, ':' );
xfree(p);
}
-print
On Wed, 23 May 2012 19:56, pk...@debian.org said:
> Indeed I do know how to decipher it[0]. However Debian did place an emphasis
> on using SHA256 instead of SHA1 (or MD5 for that matter) for signatures and
> providing a bit more visibility would've been helpful.
I changed the colon listing to a
Hi Werner,
thanks for your followup.
On Wed, May 23, 2012 at 06:28:46PM +0200, Werner Koch wrote:
> On Sat, 12 May 2012 19:34, pk...@debian.org said:
> > If I do --list-packets I get lines like this:
> >
> > digest algo 8, begin of digest cd 52
> >
> > would be very helpful if gnupg could nam
On Sat, 12 May 2012 19:34, pk...@debian.org said:
> If I do --list-packets I get lines like this:
>
> digest algo 8, begin of digest cd 52
>
> would be very helpful if gnupg could name the digest algorithm here (either
--list-packets is a GnuPG debug aid and it is expected that a developer
Package: gnupg
Version: 1.4.12-4
Severity: wishlist
If I do --list-packets I get lines like this:
digest algo 8, begin of digest cd 52
Other lines are resolving their packet argument to something readable, too. It
would be very helpful if gnupg could name the digest algorithm here (eith
5 matches
Mail list logo
