public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "tromey at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libgcj/24170] libjava natFilePosix.cc seems to have a security problem Date: Wed, 20 Feb 2008 18:39:00 -0000 [thread overview] Message-ID: <20080220183840.29057.qmail@sourceware.org> (raw) In-Reply-To: <bug-24170-7172@http.gcc.gnu.org/bugzilla/> ------- Comment #9 from tromey at gcc dot gnu dot org 2008-02-20 18:38 ------- I'll handle it. -- tromey at gcc dot gnu dot org changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|unassigned at gcc dot gnu |tromey at gcc dot gnu dot |dot org |org Status|NEW |ASSIGNED Last reconfirmed|2005-10-03 14:28:34 |2008-02-20 18:38:40 date| | http://gcc.gnu.org/bugzilla/show_bug.cgi?id=24170
next prev parent reply other threads:[~2008-02-20 18:39 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top 2005-10-02 23:12 [Bug libgcj/24170] New: [SECURITY] readdir_r considered harmful ben at decadentplace dot org dot uk 2005-10-02 23:16 ` [Bug libgcj/24170] " ben at decadentplace dot org dot uk 2005-10-03 1:01 ` Daniel Berlin 2005-10-02 23:20 ` pinskia at gcc dot gnu dot org 2005-10-02 23:28 ` [Bug libgcj/24170] natFilePosix.cc seems to have a security problem pinskia at gcc dot gnu dot org 2005-10-02 23:38 ` ben at decadentplace dot org dot uk 2005-10-03 1:01 ` dberlin at dberlin dot org 2005-10-03 14:28 ` tromey at gcc dot gnu dot org 2005-11-10 11:33 ` ben at decadentplace dot org dot uk 2008-02-20 18:28 ` [Bug libgcj/24170] libjava " jason at gcc dot gnu dot org 2008-02-20 18:39 ` tromey at gcc dot gnu dot org [this message] 2008-02-20 19:10 ` tromey at gcc dot gnu dot org 2008-02-20 19:10 ` tromey at gcc dot gnu dot 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=20080220183840.29057.qmail@sourceware.org \ --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).