The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: arnold@skeeve.com
To: tytso@mit.edu, crossd@gmail.com
Cc: tuhs@tuhs.org
Subject: [TUHS] Re: Question about BSD disklabel history
Date: Thu, 04 Jan 2024 01:42:26 -0700	[thread overview]
Message-ID: <202401040842.4048gQsN004587@freefriends.org> (raw)
In-Reply-To: <20240103163700.GA136592@mit.edu>

Things have wandered a little far afield... :-)

"Theodore Ts'o" <tytso@mit.edu> wrote:

> Or there's something running on a completely different x86 core with
> unpatched securiy bugs in the Minix and Apache cores that you can't
> even disable (unless you are the National Security Agency)....  Sadly,
> Intel refuses to make it available the magic bits to disable the Intel
> ME to anyone else.  :-(

I worked for a number of years in the design center where the firmware
and software for the ME were develped.  Although it's possible that
the firmware developers were sworn to secrecy, I never heard anything
about back doors for the NSA or anyone else.

Intel took security and code quality in the ME very seriously,
and during my tenure the quality of the ME firmware improved a lot.

ISTR that the BIOS had settings for disabling the ME. Is that
no longer true?

I know there are lots of people who despise the ME, which I never
understood. It was designed to solve the very real problem of remote
PC management, and for that it works.  My own feeling is, if you don't
want the ME, buy a processor without it; there are plenty from Intel
and AMD.

Quite seriously, and with no animosity, I'd be happy to learn what
I'm missing here.

Thanks,

Arnold

  parent reply	other threads:[~2024-01-04  8:42 UTC|newest]

Thread overview: 44+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-31 17:30 [TUHS] " Grant Taylor via TUHS
2023-12-31 17:38 ` [TUHS] " arnold
2023-12-31 20:07   ` Warner Losh
2024-01-01  0:13     ` Bakul Shah
2023-12-31 20:27   ` Phil Budne
2023-12-31 21:02     ` Warner Losh
2024-01-01  0:26   ` Grant Taylor via TUHS
2024-01-01  2:22     ` Warner Losh
2024-01-01  3:24       ` Grant Taylor via TUHS
2023-12-31 21:31 ` Clem Cole
2023-12-31 22:07   ` Warner Losh
2024-01-01 16:00     ` Clem Cole
2024-01-02 18:49       ` Warner Losh
2024-01-02 19:30         ` Chet Ramey
2024-01-02 20:07           ` Clem Cole
2024-01-02 19:50         ` Dan Cross
2024-01-02 19:55           ` Jim Capp
2024-01-02 20:11             ` Dan Cross
2024-01-02 20:30           ` Dan Cross
2024-01-02 20:50             ` Clem Cole
2024-01-02 21:04               ` Dan Cross
2023-12-31 22:46   ` G. Branden Robinson
2023-12-31 23:06     ` Larry McVoy
2023-12-31 23:37       ` Al Kossow
2023-12-31 23:41       ` Alec Muffett
2024-01-02 20:48       ` Dan Cross
2024-01-02 21:17         ` John Cowan
2024-01-03  3:33         ` Theodore Ts'o
2024-01-03  3:57           ` Warner Losh
2024-01-03  4:03             ` Warner Losh
2024-01-03  4:30             ` Theodore Ts'o
2024-01-03  5:10               ` Warner Losh
2024-01-03 15:56                 ` Dan Cross
2024-01-03 16:37                   ` Theodore Ts'o
2024-01-03 16:41                     ` Dan Cross
2024-01-04  8:42                     ` arnold [this message]
2024-01-04 18:26                       ` Kevin Bowling
2024-01-03 14:39           ` Dan Cross
2023-12-31 23:08     ` Phil Budne
2023-12-31 23:37       ` G. Branden Robinson
2023-12-31 23:59         ` Warner Losh
2023-12-31 23:50     ` G. Branden Robinson
2024-01-01  0:09       ` Al Kossow
2023-12-31 21:55 Norman Wilson

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=202401040842.4048gQsN004587@freefriends.org \
    --to=arnold@skeeve.com \
    --cc=crossd@gmail.com \
    --cc=tuhs@tuhs.org \
    --cc=tytso@mit.edu \
    /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).