linux-kernel - Re: Does /dev/urandom now block until initialised ?

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:   Mon, 23 Jul 2018 12:11:12 -0400
From:   Jeffrey Walton <noloader@...il.com>
To:     "Theodore Y. Ts'o" <tytso@....edu>,
        Ken Moffat <zarniwhoop73@...glemail.com>,
        Linux Crypto Mailing List <linux-crypto@...r.kernel.org>,
        lkml <linux-kernel@...r.kernel.org>
Subject: Re: Does /dev/urandom now block until initialised ?

On Mon, Jul 23, 2018 at 11:16 AM, Theodore Y. Ts'o <tytso@....edu> wrote:
> On Mon, Jul 23, 2018 at 04:43:01AM +0100, Ken Moffat wrote:
>> ...
> One of the reasons why I didn't see the problem when I was developing
> the remediation patch for CVE-2018-1108 is because I run Debian
> testing, which doesn't have this particular Red Hat patch.

Off-topic, I'm kind of surprised it took that long to fix it (if I am
parsing things correctly).

I believe Stephan Mueller wrote up the weakness a couple of years ago.
He's the one who explained the interactions to me. Mueller was even
cited at https://github.com/systemd/systemd/issues/4167.

It is too bad he Mueller not receive credit for it in the CVE database.

Jeff