Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Date: Thu, 18 Aug 2016 19:54:52 +0300
From: Solar Designer <>
Subject: Re: Libgcrypt and GnuPG 1.4 RNG output prediction

Here's what Werner wrote in that message, regarding the CVE ID:
> Sorry, that was my typo.  It is correct in the NEWS files and the commit
> messages.
> The reseachers forwarded me a mail with the CVE but I have not been put
> the loop, neither from RedHat, nor from Debian (as they usually do).

More interesting are these tweets:

<@gnupg> @hanno They will present their paper at  A preprint can now be found here:
<gnupg> The paper about the Libgcrypt RNG bug has meanwhile been published:\n

On Thu, Aug 18, 2016 at 05:37:20PM +0100, Andrew Gallagher wrote:
> Werner used PGP/MIME, but something appears to have deleted the first
> mime-boundary, rendering the message unparseable. If you view the
> source you can see the plaintext, but MIME mail clients (including the
> openwall mailing list archive) can't.

Yes, unfortunately.  I investigated this yesterday, and it appears to be
a long-standing bug in ezmlm-idx (hopefully already patched in newer
versions, but I didn't check), which is triggered by Gnus, depending on
a combination of settings on both sides - specifically, when a MIME
section does not include a Content-Type header, yet the list is
configured to remove sections with some MIME types.  The MIME type
should then default to text/plain, and the section preserved, but
ezmlm-idx would forget to set a flag indicating that such section is OK
to keep.  I think I've patched this on the server now, but I didn't
test.  Previous discoveries of the bug:


Powered by blists - more mailing lists

Please check out the Open Source Software Security Wiki, which is counterpart to this mailing list.

Confused about mailing lists and their use? Read about mailing lists on Wikipedia and check out these guidelines on proper formatting of your messages.