From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 114425 invoked by alias); 6 Oct 2015 15:36:12 -0000 Mailing-List: contact glibc-bugs-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Post: List-Help: , Sender: glibc-bugs-owner@sourceware.org Received: (qmail 114382 invoked by uid 48); 6 Oct 2015 15:36:09 -0000 From: "archie.cobbs at gmail dot com" To: glibc-bugs@sourceware.org Subject: [Bug libc/3662] Implementation bugs in random_r and friends Date: Tue, 06 Oct 2015 15:36:00 -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.4 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: archie.cobbs at gmail 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: cc Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Bugzilla-URL: http://sourceware.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-SW-Source: 2015-10/txt/msg00085.txt.bz2 https://sourceware.org/bugzilla/show_bug.cgi?id=3662 Archie Cobbs changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |archie.cobbs at gmail dot com --- Comment #10 from Archie Cobbs --- Through a long and painful process of debugging and hair-pulling I also arrived at this issue. I am now in a state of weary disbelief. > I already said no. The interfaces are used internally and that's really > their only purpose. Design and implement your own library with randomization > functions if you must. If you don't want to provide any more patches to > the documentation the bug might as well be closed. WTF are you talking about? These functions are exposed and documented as normal library functions just like all the others: NAME random_r, srandom_r, initstate_r, setstate_r - reentrant random number generator ... DESCRIPTION These functions are the reentrant equivalents of the functions described in random(3). They are suitable for use in multithreaded programs where each thread needs to obtain an independent, reproducible sequence of random numbers. This is a malevolent segfault booby-trap! I can't believe the maintainers of glibc don't care. -- You are receiving this mail because: You are on the CC list for the bug.