All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Arjan van de Ven <arjan@infradead.org>
Cc: Ben Ford <ben@kalifornia.com>, linux-kernel@vger.kernel.org
Subject: Re: Who wants to test cracklinux??
Date: Mon, 03 Apr 2006 00:16:11 +0100	[thread overview]
Message-ID: <1144019771.31123.31.camel@localhost.localdomain> (raw)
In-Reply-To: <1144017581.3066.34.camel@testmachine>

On Llu, 2006-04-03 at 00:39 +0200, Arjan van de Ven wrote:
> is there any difference? I mean... if you can outb you for all intents
> and purposes are root anyway ;) (like you can overwrite any memory in
> the system etc etc)

There are two clear uses

#1	Its possible to write such a module to allow only some ports to be
accessed, eg to export a PCI device for learning purposes

#2	As root you can make mistakes and mess up a box. Having the ability
to do stuff and having the default as "its allowed" differ. Giving
someone iopl rights is a bit like giving someone sudo. The security
against active attack is unchanged, the security against screwups is
higher


Alan


  parent reply	other threads:[~2006-04-02 23:08 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-28 20:12 Who wants to test cracklinux?? Marko
2006-03-28 22:01 ` Sam Ravnborg
2006-03-28 22:49 ` Pavel Machek
2006-03-28 23:49   ` Måns Rullgård
2006-03-29 12:02     ` Jan Engelhardt
2006-03-29 12:32     ` Marko Euth
2006-04-02 22:34   ` Ben Ford
2006-04-02 22:39     ` Arjan van de Ven
2006-04-02 23:07       ` Marko Euth
2006-04-02 23:16       ` Alan Cox [this message]
2006-04-03  9:11         ` Jan Engelhardt

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=1144019771.31123.31.camel@localhost.localdomain \
    --to=alan@lxorguk.ukuu.org.uk \
    --cc=arjan@infradead.org \
    --cc=ben@kalifornia.com \
    --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.