From: Dan Cross <email@example.com>
To: Alec Muffett <firstname.lastname@example.org>
Cc: TUHS <email@example.com>
Subject: [TUHS] Re: In search of SunOS 4-era security advisory.
Date: Wed, 11 Jan 2023 12:30:45 -0500 [thread overview]
Message-ID: <CAEoi9W7RsX3dzk3cPmi08ReA5FKgNGoZYHn2Qs+9gOAEr4ksJw@mail.gmail.com> (raw)
That's it. Thanks, Alec!
On Wed, Jan 11, 2023 at 12:28 PM Alec Muffett <firstname.lastname@example.org> wrote:
> On Wed, 11 Jan 2023, 17:13 Dan Cross, <email@example.com> wrote:
>> The security vulnerability in question could be briefly summarized as,
>> "Fortran divide-by-zero gives root." I think that was just a specific
>> manifestation of the underlying problem, though. More specifically it
>> was actually due to failure to sanitize state after handling a SIGFPE
>> (and possibly other signals as well?).
>> I have a distinct memory of this, but can no longer find any evidence
>> for it. Did I just make it up from whole cloth, or was this actually a
>> - Dan C.
prev parent reply other threads:[~2023-01-11 17:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-11 17:11 [TUHS] " Dan Cross
2023-01-11 17:27 ` [TUHS] " Alec Muffett
2023-01-11 17:30 ` Dan Cross [this message]
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:
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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 NNTP newsgroup(s).