From: Ingo Oeser <ioe-lkml@rameria.de>
To: "linux-os \(Dick Johnson\)" <linux-os@analogic.com>
Cc: "Ed White" <ed.white@libero.it>, "ML" <linux-kernel@vger.kernel.org>
Subject: Re: SecurityFocus Article
Date: Thu, 11 May 2006 22:03:46 +0200 [thread overview]
Message-ID: <200605112203.46996.ioe-lkml@rameria.de> (raw)
In-Reply-To: <Pine.LNX.4.61.0605111140030.3833@chaos.analogic.com>
Hi,
On Thursday, 11. May 2006 17:47, linux-os (Dick Johnson) wrote:
> If the SMRAM control register exists, the D_LCK bit can be set
> in 16-bit mode during the boot sequence. This makes the SMRAM
> register read/only so the long potential compromise sequence
> that Mr. Duflot describes would not be possible. If the control
> register doesn't exist, then the vulnerably doesn't exist.
>
> The writer doesn't like the fact that a root process can execute
> iopl(3) and then be able to read/write ports. He doesn't like
> the fact that the X-server can read/write ports from user-mode.
>
> Sorry, the X-server is too large to go into the kernel. It's
> a lot easier to modify the boot-loader to set the D_LCK bit
> if the security compromise turns out to be real.
That sounds like a good move.
Any patches?
I would love to review them!
Regards
Ingo Oeser
next prev parent reply other threads:[~2006-05-11 20:06 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-11 14:34 SecurityFocus Article Ed White
2006-05-11 15:06 ` Andi Kleen
2006-05-11 15:32 ` Alan Cox
2006-05-11 15:47 ` linux-os (Dick Johnson)
2006-05-11 20:03 ` Ingo Oeser [this message]
2006-05-12 0:19 ` Segher Boessenkool
2006-05-12 3:17 ` Jon Smirl
2006-05-12 4:13 ` Dave Airlie
2006-05-12 5:07 ` Jon Smirl
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=200605112203.46996.ioe-lkml@rameria.de \
--to=ioe-lkml@rameria.de \
--cc=ed.white@libero.it \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-os@analogic.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 NNTP newsgroup(s).