public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Marko Euth <letterdrop@gmx.de>
To: linux-kernel@vger.kernel.org
Cc: Arjan van de Ven <arjan@infradead.org>, Ben Ford <ben@kalifornia.com>
Subject: Re: Who wants to test cracklinux??
Date: Mon, 3 Apr 2006 01:07:09 +0200	[thread overview]
Message-ID: <20060403010709.9f611253.letterdrop@gmx.de> (raw)
In-Reply-To: <1144017581.3066.34.camel@testmachine>

On Mon, 03 Apr 2006 00:39:41 +0200
Arjan van de Ven <arjan@infradead.org> wrote:

> On Sun, 2006-04-02 at 15:34 -0700, Ben Ford wrote:
> > -----BEGIN PGP SIGNED MESSAGE-----
> > Hash: SHA1
> > 
> > Pavel Machek wrote:
> > > Hi!
> > >> I've written a small kernel module & shared object for kernel 2.6 to
> > >> enable the following for normal users:
> > >>
> > >> - inb()/outb()... via a wrapper function
> > > ioperm() does that already, no? You mean, you enable it for non-root,
> > > too? That's security hole.
> > 
> > My OS development classes have a lab of machines that run entirely as
> > root just for these reasons.  I think it's valid to allow these
> > operations as non-root in certain situations.  It is better than
> > running *everything* as root, no?

Yes, that's exactly what the whole module is meant for.

> 
> 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)
> 

Don't you think beeing root is a little bit more
easy than doing everything with outb??? ;))


  reply	other threads:[~2006-04-02 23:07 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 [this message]
2006-04-02 23:16       ` Alan Cox
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=20060403010709.9f611253.letterdrop@gmx.de \
    --to=letterdrop@gmx.de \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox