All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Ed White <ed.white@libero.it>
Cc: ML <linux-kernel@vger.kernel.org>
Subject: Re: SecurityFocus Article
Date: Thu, 11 May 2006 16:32:38 +0100	[thread overview]
Message-ID: <1147361558.26130.30.camel@localhost.localdomain> (raw)
In-Reply-To: <20060511143440.23517.qmail@securityfocus.com>

On Iau, 2006-05-11 at 14:34 +0000, Ed White wrote:
> The big problem is that the attack is possible thanks to the way X
> Windows is designed

Where did you get that idea.

What it essentially says is "if you can hack the machine enough to get
the ability to issue raw i/o accesses you can get any other power you
want". Thats always been true. Using SMM to do this seems awfully hard
work.

Alan


  parent reply	other threads:[~2006-05-11 15:20 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 [this message]
2006-05-11 15:47 ` linux-os (Dick Johnson)
2006-05-11 20:03   ` Ingo Oeser
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=1147361558.26130.30.camel@localhost.localdomain \
    --to=alan@lxorguk.ukuu.org.uk \
    --cc=ed.white@libero.it \
    --cc=linux-kernel@vger.kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.