From: Siddhesh Poyarekar <siddhesh@gotplt.org>
To: Richard Earnshaw <Richard.Earnshaw@foss.arm.com>,
Binutils Mailing List <binutils@sourceware.org>,
gdb@sourceware.org
Cc: Nick Clifton <nickc@redhat.com>
Subject: Re: Threat model for GNU Binutils
Date: Mon, 17 Apr 2023 12:22:15 -0400 [thread overview]
Message-ID: <6d7dbfcb-cf92-8474-087e-0b2238a76188@gotplt.org> (raw)
In-Reply-To: <1a4953e1-7c23-79be-9d4e-249f49f48ff0@gotplt.org>
On 2023-04-17 12:17, Siddhesh Poyarekar wrote:
> The glibc security exceptions[3] are a good example of how this is
> typically done.
I should clarify that as far as I am aware, the glibc security
exceptions are not a result of a threat modeling exercise; I quoted it
as an example of how one could define contexts under which library
interfaces may be supported for use.
Sid
next prev parent reply other threads:[~2023-04-17 16:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-14 13:12 Richard Earnshaw
2023-04-14 14:08 ` Siddhesh Poyarekar
2023-04-14 14:41 ` Richard Earnshaw
2023-04-17 16:17 ` Siddhesh Poyarekar
2023-04-17 16:22 ` Siddhesh Poyarekar [this message]
2023-04-14 15:07 ` Richard Earnshaw
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=6d7dbfcb-cf92-8474-087e-0b2238a76188@gotplt.org \
--to=siddhesh@gotplt.org \
--cc=Richard.Earnshaw@foss.arm.com \
--cc=binutils@sourceware.org \
--cc=gdb@sourceware.org \
--cc=nickc@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: link
Be 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).