public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libstdc++/65142] std::random_device Ignores Read Return Code (CVE-2015-5276) Date: Thu, 17 Sep 2015 15:07:00 -0000 [thread overview] Message-ID: <bug-65142-4-uefZ7QEvaI@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-65142-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65142 --- Comment #11 from Jonathan Wakely <redi at gcc dot gnu.org> --- Author: redi Date: Thu Sep 17 15:06:42 2015 New Revision: 227872 URL: https://gcc.gnu.org/viewcvs?rev=227872&root=gcc&view=rev Log: Make std::random_device retry after short reads PR libstdc++/65142 * src/c++11/random.cc (random_device::_M_getval()): Retry after short reads. Modified: trunk/libstdc++-v3/ChangeLog trunk/libstdc++-v3/src/c++11/random.cc
next prev parent reply other threads:[~2015-09-17 15:07 UTC|newest] Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-65142-4@http.gcc.gnu.org/bugzilla/> 2015-02-20 16:53 ` [Bug libstdc++/65142] std::random_device Ignores Read Return Code redi at gcc dot gnu.org 2015-02-20 16:58 ` redi at gcc dot gnu.org 2015-09-11 13:30 ` redi at gcc dot gnu.org 2015-09-11 13:44 ` redi at gcc dot gnu.org 2015-09-11 13:45 ` redi at gcc dot gnu.org 2015-09-14 14:47 ` fweimer at redhat dot com 2015-09-14 15:03 ` redi at gcc dot gnu.org 2015-09-15 10:39 ` rguenth at gcc dot gnu.org 2015-09-15 11:44 ` redi at gcc dot gnu.org 2015-09-15 11:50 ` redi at gcc dot gnu.org 2015-09-15 12:12 ` rguenther at suse dot de 2015-09-17 15:07 ` redi at gcc dot gnu.org [this message] 2015-10-02 13:00 ` [Bug libstdc++/65142] std::random_device Ignores Read Return Code (CVE-2015-5276) rguenth at gcc dot gnu.org 2015-10-02 20:08 ` redi at gcc dot gnu.org 2015-10-02 20:11 ` redi at gcc dot gnu.org 2015-10-02 20:15 ` fw at gcc dot gnu.org 2015-10-02 20:52 ` redi at gcc dot gnu.org 2015-10-02 20:53 ` redi at gcc dot gnu.org
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-65142-4-uefZ7QEvaI@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.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).