From: John DeGood <john@degood.org>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] punched cards live
Date: Mon, 3 Nov 2008 08:37:22 -0500 [thread overview]
Message-ID: <490EFE92.9060707@degood.org> (raw)
In-Reply-To: <13426df10811022301p15fcc7edj9c6a7718aad62f5c@mail.gmail.com>
It's the ACPI Secure Computing Initiative: fixed input format == no
buffer overflow vulnerabilities. Long live Herman Hollerith!
ron minnich wrote:
> This courtesy of the ACPI spec: ""RSD PTR " (Notice that this
> signature must contain a trailing
> blank character.)"
>
> So where do we get the guys who design this stuff? Can we send them
> back? Or put them in an infinite loop in a time machine (oh wait see
> the subject).
>
> ron
>
next prev parent reply other threads:[~2008-11-03 13:37 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-03 7:01 ron minnich
2008-11-03 12:06 ` erik quanstrom
2008-11-03 13:29 ` Brantley Coile
2008-11-03 13:37 ` John DeGood [this message]
2008-11-03 13:59 erik quanstrom
2008-11-04 15:25 Eris Discordia
[not found] <1CF8271E0E449545D858FAB3@192.168.1.2>
2008-11-04 16:25 ` David Leimbach
2008-11-05 10:39 ` Eris Discordia
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=490EFE92.9060707@degood.org \
--to=john@degood.org \
--cc=9fans@9fans.net \
/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 NNTP newsgroup(s).