All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ben Ford <ben@kalifornia.com>
To: linux-kernel@vger.kernel.org
Subject: Re: Who wants to test cracklinux??
Date: Sun, 02 Apr 2006 15:34:59 -0700	[thread overview]
Message-ID: <44305193.5080408@kalifornia.com> (raw)
In-Reply-To: <20060328224929.GC5760@elf.ucw.cz>

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

- -b

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2.2 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFEMFGSInEozL1f7FIRAif7AJ41yzdVRHpiGU3Mqy8ef3aZ4TGNVACfYyED
xfZzMo2d5RFO80ciQ1YSo68=
=JKdo
-----END PGP SIGNATURE-----


  parent reply	other threads:[~2006-04-02 22:35 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 [this message]
2006-04-02 22:39     ` Arjan van de Ven
2006-04-02 23:07       ` Marko Euth
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=44305193.5080408@kalifornia.com \
    --to=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.