git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [PATCH 12/12] config.mak.uname: add a note about CSPRNG_METHOD for Linux

From
Ramsay Jones <ramsay@ramsayjones.plus.com>
Date
Mar 16, 2025, 21:57 UTC
Message-ID
<9c815bdc-4cc6-4614-a203-105811ebbb59@ramsayjones.plus.com>
In-Reply-To
<xmqqr02wbtdn.fsf@gitster.g>
On 16/03/2025 20:41, Junio C Hamano wrote:
Show 25 quoted lines
> "brian m. carlson" <sandals@crustytoothpaste.net> writes:
> 
>> When arc4random was added to glibc, the Linux kernel CSPRNG maintainer
>> argued that it was not a secure approach (I disagree), and convinced the
>> glibc maintainers to just make it a wrapper around the Linux kernel
>> CSPRNG, which it now is.  So there's no actual benefit to calling
>> arc4random versus getrandom, and since it's newer and less commonly
>> available than getrandom, as well as slightly slower (because of an
>> extra function call), getrandom should be preferred.
> 
> This
> 
> https://www.phoronix.com/news/GNU-Glibc-arc4random-Functions
> 
> was the first hit of my search in the area, but I think you are
> referring to
> 
> https://sourceware.org/git/?p=glibc.git;a=commitdiff;h=eaad4f9
> 
> that happened 5 days after the thing got in and the code there tells
> me that your summary of the situation is quite accurate.
> 
> So I agree that dropping this patch makes sense, but do we want to
> do a bit more to improve the situation?
> 

Yes, this patch should be dropped. (See my reply to Brian; our emails crossed!).

ATB, Ramsay Jones

Previous: Junio C HamanoNext: Patrick Steinhardt
Message 4 of 10 in “config.mak.uname: add a note about CSPRNG_METHOD for Linux”
  1. 12/12 config.mak.uname: add a note about CSPRNG_METHOD for LinuxRamsay Jones, Mar 15, 2025
  2. brian m. carlsonMar 16, 2025
  3. Junio C HamanoMar 16, 2025
  4. Ramsay JonesMar 16, 2025
  5. Patrick SteinhardtMar 19, 2025
  6. Ramsay JonesMar 20, 2025
  7. Patrick SteinhardtMar 20, 2025
  8. Ramsay JonesMar 20, 2025
  9. Ramsay JonesMar 16, 2025
  10. brian m. carlsonMar 16, 2025

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.