From: mark gross <mgross@linux.intel.com>
To: speck@linutronix.de
Subject: [MODERATED] test email
Date: Thu, 28 Feb 2019 10:19:24 -0800 [thread overview]
Message-ID: <20190228181924.GA7752@mgross-MOBL.amr.corp.intel.com> (raw)
just some junk I had from a web page to test
[$] GMP and assert()
[Security] Posted Feb 27, 2019 21:11 UTC (Wed) by jake
A report of a potential security problem in the GNU Multiple Precision
Arithmetic (GMP) library was met with a mixed reaction, from skepticism to
responses verging on hostility, but the report ultimately raised a question
worth pondering. What role should assertions (i.e. calls to the POSIX assert()
macro) play in error handling? An assertion that fails leads to a process exit,
which may not be what a developer calling into a library expects. Unexpected
behavior is, of course, one step on a path that can lead to security holes.
Full Story (comments: 14)
reply other threads:[~2019-02-28 18:19 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20190228181924.GA7752@mgross-MOBL.amr.corp.intel.com \
--to=mgross@linux.intel.com \
--cc=speck@linutronix.de \
/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).