public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "drepper at redhat dot com" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sources.redhat.com Subject: [Bug libc/567] resolv/base64.c does not correctly decode, does not check parameters & overwrites bytes after target Date: Mon, 26 Sep 2005 16:21:00 -0000 [thread overview] Message-ID: <20050926162123.30059.qmail@sourceware.org> (raw) In-Reply-To: <20041122145010.567.gemenge@hotmail.com> ------- Additional Comments From drepper at redhat dot com 2005-09-26 16:21 ------- You have to provide a test case for what is wrong. Linking to a file from the glibc sources would be OK, too, it does not have to link against the glibc DSO itself. -- What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |WAITING http://sourceware.org/bugzilla/show_bug.cgi?id=567 ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
next prev parent reply other threads:[~2005-09-26 16:21 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2004-11-22 14:51 [Bug libc/567] New: " gemenge@hotmail.com 2005-09-26 16:21 ` drepper at redhat dot com [this message] 2006-04-25 18:15 ` [Bug libc/567] " drepper 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=20050926162123.30059.qmail@sourceware.org \ --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).