From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <sourceware-bugzilla@sourceware.org>
Received: by sourceware.org (Postfix, from userid 48)
 id BB8E0385801E; Mon,  8 Aug 2022 12:45:13 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org BB8E0385801E
From: "jason at zx2c4 dot com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug libc/29437] arc4random is too slow
Date: Mon, 08 Aug 2022 12:45:13 +0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: glibc
X-Bugzilla-Component: libc
X-Bugzilla-Version: 2.36
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jason at zx2c4 dot com
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: unassigned at sourceware dot org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags: security-
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-29437-131-3VMpMRe6uB@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-29437-131@http.sourceware.org/bugzilla/>
References: <bug-29437-131@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-BeenThere: glibc-bugs@sourceware.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Glibc-bugs mailing list <glibc-bugs.sourceware.org>
List-Unsubscribe: <https://sourceware.org/mailman/options/glibc-bugs>,
 <mailto:glibc-bugs-request@sourceware.org?subject=unsubscribe>
List-Archive: <https://sourceware.org/pipermail/glibc-bugs/>
List-Help: <mailto:glibc-bugs-request@sourceware.org?subject=help>
List-Subscribe: <https://sourceware.org/mailman/listinfo/glibc-bugs>,
 <mailto:glibc-bugs-request@sourceware.org?subject=subscribe>
X-List-Received-Date: Mon, 08 Aug 2022 12:45:13 -0000

https://sourceware.org/bugzilla/show_bug.cgi?id=3D29437

--- Comment #14 from Jason A. Donenfeld <jason at zx2c4 dot com> ---
> So the question is should we trade performance or correctness?

Or do neither, and just hold your horses until we can sort this vDSO stuff =
out
in the kernel? That might take some time, but remember: arc4random() didn't
even exist in glibc a few weeks ago. It was you all who rushed this in over=
 my
objections. Don't now follow that bad decision making to its next bad step =
of
introducing intentional correctness issues. Instead just chill out for a li=
ttle
bit, don't take further actions, and let's see what is possible in the kern=
el.

Just stop spinning your wheels over this stuff for a while, okay?

--=20
You are receiving this mail because:
You are on the CC list for the bug.=