public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "adhemerval.zanella at linaro dot org" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sourceware.org Subject: [Bug libc/15813] Multiple issues in __gen_tempname Date: Wed, 09 Sep 2020 13:30:10 +0000 [thread overview] Message-ID: <bug-15813-131-Zt26yPmjpP@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-15813-131@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=15813 --- Comment #10 from Adhemerval Zanella <adhemerval.zanella at linaro dot org> --- I meant the updated gnulib version from its repository, not the outdated version glibc packs now. The gnulib version currently does not use neither the process pid nor the clock for source of entropy, it uses either getrandom or a simple linear congruential generator if getrandom fails. I think using getentropy where available should make it more robust. These interface contains inherent concurrent issues and applications should either use O_TMPFILE or at leat tmpfile. -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2020-09-09 13:30 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top 2013-08-02 5:16 [Bug libc/15813] New: " bugdal at aerifal dot cx 2013-10-11 21:25 ` [Bug libc/15813] " neleai at seznam dot cz 2013-10-11 21:29 ` bugdal at aerifal dot cx 2014-06-13 13:16 ` fweimer at redhat dot com 2020-09-09 9:37 ` jakub at redhat dot com 2020-09-09 9:51 ` jakub at redhat dot com 2020-09-09 12:19 ` adhemerval.zanella at linaro dot org 2020-09-09 12:35 ` kdudka at redhat dot com 2020-09-09 12:44 ` jakub at redhat dot com 2020-09-09 13:30 ` adhemerval.zanella at linaro dot org [this message] 2020-09-15 13:38 ` carlos at redhat dot com 2020-09-22 13:14 ` fweimer at redhat dot com 2020-09-22 13:15 ` fweimer at redhat dot com
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=bug-15813-131-Zt26yPmjpP@http.sourceware.org/bugzilla/ \ --to=sourceware-bugzilla@sourceware.org \ --cc=glibc-bugs@sourceware.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).