linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: John Myers <electronerd@monolith3d.com>
To: Christer Weinigel <christer@weinigel.se>
Cc: Pascal Schmidt <der.eremit@email.de>,
	Joerg Schilling <schilling@fokus.fraunhofer.de>,
	linux-kernel@vger.kernel.org, Jens Axboe <axboe@suse.de>
Subject: (was: Re: PATCH: cdrecord: avoiding scsi device numbering for ide devices)
Date: Tue, 31 Aug 2004 15:22:03 -0700	[thread overview]
Message-ID: <4134FA0B.6030404@monolith3d.com> (raw)
In-Reply-To: <m37jrr40zi.fsf@zoo.weinigel.se>

[-- Attachment #1: Type: text/plain, Size: 2124 bytes --]

Christer Weinigel wrote:

> Pascal Schmidt <der.eremit@email.de> writes:

> [...] if I have write permisson to a CD burner, being able to
> burn a coaster by issuing strange commands is something I expect.
> Being able to destroy the firmware of the drive is not something I
> expect a normal user to be able to do.
> 
> There are at least three conflicting goals here:
> 
> 1. Only someone with CAP_SYS_RAWIO (i.e. root) should be able to do
>    possible destructive things to a device, and only root should be
>    able to bypass the normal security checks in the kernel (e.g. get
>    access to /dev/mem since access to it means that you can read and
>    modify internal kernel structures).
> 
> 2. A Linux system should have as few suid root binaries as possible.
> 
> 3. A normal user should be able to perform most tasks without needing
>    root.
> 

I hope this is not a stupid idea:

I propose a finer-grained approach to suid-root binaries. Perhaps, 
instead of having a single flag giving the binary all the rights and 
responsibilities of its owner, there could be a table/list/something of 
capabilities which we want to grant to the binary. This, of course, 
would be a privileged operation (perhaps a new capability?).

For example, we might want to grant cdrecord CAP_SYS_RAWIO. This way, we 
don't have to worry about cdrecord running as root and not dropping all 
the capabilities it doesn't need, by accident or by malice.

Further, and I realize that this would probably require major 
restructuring, perhaps there could be another field: for each capability 
we want to grant, a method to specify _where_ the binary can use that 
capability.

To extend the previous example: we might want to give cdrecord 
CAP_SYS_RAWIO just on, say, /dev/burner0 and /dev/burner1, but not 
/dev/hda. That way, some typo won't have us trying to burn cds with our 
hard disks.

Again, I hope it's not a stupid idea. I don't have a working 
implementation, and I'm not even sure if it's even possible, but it's a 
thought.
-- 
electronerd (jonathan s myers)
code poet and recycle bin monitor
programmer, monolith3d.com

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 254 bytes --]

  parent reply	other threads:[~2004-08-31 22:27 UTC|newest]

Thread overview: 50+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <2ptdY-42Y-55@gated-at.bofh.it>
     [not found] ` <2uPdM-380-11@gated-at.bofh.it>
     [not found]   ` <2uUwL-6VP-11@gated-at.bofh.it>
     [not found]     ` <2uWfh-8jo-29@gated-at.bofh.it>
     [not found]       ` <2uXl0-Gt-27@gated-at.bofh.it>
     [not found]         ` <2vge2-63k-15@gated-at.bofh.it>
     [not found]           ` <2vgQF-6Ai-39@gated-at.bofh.it>
     [not found]             ` <2vipq-7O8-15@gated-at.bofh.it>
     [not found]               ` <2vj2b-8md-9@gated-at.bofh.it>
     [not found]                 ` <2vDtS-bq-19@gated-at.bofh.it>
2004-08-21 15:01                   ` PATCH: cdrecord: avoiding scsi device numbering for ide devices Pascal Schmidt
2004-08-21 15:57                     ` Joerg Schilling
2004-08-21 21:42                       ` Pascal Schmidt
2004-08-22 11:56                       ` Joerg Schilling
2004-08-22 12:14                         ` Joerg Schilling
2004-08-22 12:52                           ` Patrick McFarland
2004-08-22 13:05                             ` Joerg Schilling
2004-08-22 16:38                               ` Horst von Brand
2004-08-22 15:11                           ` Horst von Brand
2004-08-22 18:09                             ` Matthias Andree
2004-08-22 13:13                         ` Pascal Schmidt
2004-08-22 16:00                           ` Christer Weinigel
2004-08-22 16:32                             ` Joerg Schilling
2004-08-22 17:18                               ` Christer Weinigel
2004-08-22 19:22                                 ` DTrace-like analysis possible with future Linux kernels? Joerg Schilling
2004-08-22 20:27                               ` PATCH: cdrecord: avoiding scsi device numbering for ide devices Giuseppe Bilotta
2004-08-22 21:29                               ` Julien Oster
2004-08-23 11:40                                 ` Joerg Schilling
2004-08-23 13:15                                   ` Matthias Andree
2004-08-23 18:16                               ` Kai Makisara
2004-08-24 10:22                                 ` Christer Weinigel
2004-08-24 15:34                                 ` Joerg Schilling
2004-08-22 16:33                             ` Christer Weinigel
2004-08-22 16:19                               ` Alan Cox
2004-08-22 17:31                                 ` Christer Weinigel
2004-08-22 20:47                                   ` Alan Cox
2004-08-22 22:17                                     ` Christer Weinigel
2004-08-23 12:22                                 ` Adam Sampson
2004-08-22 19:26                             ` Tonnerre
2004-08-22 20:14                               ` DTrace-like analysis possible with future Linux kernels? Joerg Schilling
2004-08-22 20:33                                 ` Tonnerre
2004-08-22 20:38                                   ` Alan Cox
2004-08-22 20:43                                   ` Joerg Schilling
2004-08-22 21:37                                     ` Christer Weinigel
2004-08-23 11:44                                       ` Joerg Schilling
2004-08-23 17:40                                 ` Horst von Brand
2004-08-23 20:25                               ` PATCH: cdrecord: avoiding scsi device numbering for ide devices Bill Davidsen
2004-08-23 21:01                                 ` Doug Maxey
2004-08-25 18:29                                   ` Bill Davidsen
2004-08-24  2:22                                 ` Nuno Silva
2004-08-31 22:22                             ` John Myers [this message]
2004-09-02  9:44                               ` (was: Re: PATCH: cdrecord: avoiding scsi device numbering for ide devices) Joerg Schilling
2004-09-02 13:49                                 ` John Myers
2004-09-02 15:40                                   ` Joerg Schilling
2004-08-22 21:27                           ` PATCH: cdrecord: avoiding scsi device numbering for ide devices Julien Oster
2004-08-07 12:51 Linux Kernel bug report (includes fix) Joerg Schilling
2004-08-07 13:26 ` Måns Rullgård
2004-08-07 19:32   ` Bernd Schubert
2004-08-08  1:18 ` Horst von Brand
2004-08-08  5:22   ` Alexander E. Patrakov

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=4134FA0B.6030404@monolith3d.com \
    --to=electronerd@monolith3d.com \
    --cc=axboe@suse.de \
    --cc=christer@weinigel.se \
    --cc=der.eremit@email.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=schilling@fokus.fraunhofer.de \
    /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).