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/21892] New: gnu.* and native code security audit Date: Thu, 02 Jun 2005 22:43:00 -0000 [thread overview] Message-ID: <20050602224341.21892.tromey@gcc.gnu.org> (raw) In order to be confident in our security implementation we must ensure that calls to gnu.* code (which might bypass security checks) are inaccessible to user code running in a secure context. Some sort of automated testing would be ideal, so that we could reliably re-run the audit whenever we like. That will ensure we don't have a (disastrous) regression here. Likewise we must audit the CNI code for things like buffer overflows. -- Summary: gnu.* and native code security audit Product: gcc Version: 4.1.0 Status: UNCONFIRMED Severity: normal Priority: P2 Component: libgcj AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: tromey at gcc dot gnu dot org CC: gcc-bugs at gcc dot gnu dot org,java-prs at gcc dot gnu dot org OtherBugsDependingO 13603 nThis: http://gcc.gnu.org/bugzilla/show_bug.cgi?id=21892
next reply other threads:[~2005-06-02 22:43 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2005-06-02 22:43 tromey at gcc dot gnu dot org [this message] 2005-06-03 6:14 ` [Bug libgcj/21892] " konqueror at gmx dot de 2005-06-03 15:13 ` tromey at gcc dot gnu dot org 2005-06-19 14:25 ` pinskia at gcc dot gnu dot org 2005-07-13 17:20 ` 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=20050602224341.21892.tromey@gcc.gnu.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).