public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "fweimer at redhat dot com" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sources.redhat.com Subject: [Bug libc/14699] readdir_r: does not enforce NAME_MAX limit Date: Fri, 12 Oct 2012 11:48:00 -0000 [thread overview] Message-ID: <bug-14699-131-y5rdNCauC2@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-14699-131@http.sourceware.org/bugzilla/> http://sourceware.org/bugzilla/show_bug.cgi?id=14699 --- Comment #1 from Florian Weimer <fweimer at redhat dot com> 2012-10-12 11:48:29 UTC --- This is somewhat related to bug 11333. For architectures where the fix is active, the name is clipped and not properly NUL-terminated. -- Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
next prev parent reply other threads:[~2012-10-12 11:48 UTC|newest] Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-10-11 9:49 [Bug libc/14699] New: " fweimer at redhat dot com 2012-10-11 14:42 ` [Bug libc/14699] " fweimer at redhat dot com 2012-10-12 11:48 ` fweimer at redhat dot com [this message] 2012-11-29 15:06 ` fweimer at redhat dot com 2012-11-29 16:03 ` fweimer at redhat dot com 2013-05-09 14:58 ` aj at suse dot de 2013-05-14 11:34 ` fweimer at redhat dot com 2013-08-16 13:38 ` fweimer at redhat dot com 2013-10-25 14:00 ` cvs-commit at gcc dot gnu.org 2013-11-01 19:01 ` cvs-commit at gcc dot gnu.org 2013-11-21 17:16 ` cvs-commit at gcc dot gnu.org 2014-01-06 16:55 ` cvs-commit at gcc dot gnu.org 2014-01-06 16:56 ` cvs-commit at gcc dot gnu.org 2014-06-12 18:53 ` [Bug libc/14699] readdir_r: does not enforce NAME_MAX limit (CVE-2013-4237) fweimer at redhat dot com 2014-06-30 18:44 ` fweimer at redhat dot com 2015-01-16 16:59 ` cvs-commit at gcc dot gnu.org 2015-01-29 18:49 ` cvs-commit at gcc dot gnu.org 2015-02-23 15:03 ` cvs-commit at gcc dot gnu.org 2015-02-24 10:56 ` 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-14699-131-y5rdNCauC2@http.sourceware.org/bugzilla/ \ --to=sourceware-bugzilla@sourceware.org \ --cc=glibc-bugs@sources.redhat.com \ /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).