From: Christer Weinigel <christer@weinigel.se>
To: Frank Steiner <fsteiner-mail@bio.ifi.lmu.de>
Cc: Marc Ballarin <Ballarin.Marc@gmx.de>,
Alan Cox <alan@lxorguk.ukuu.org.uk>,
jwendel10@comcast.net, linux-kernel@vger.kernel.org,
Kai.Makisara@kolumbus.fi
Subject: Re: 2.6.8.1 Mis-detect CRDW as CDROM
Date: 17 Aug 2004 13:29:45 +0200 [thread overview]
Message-ID: <m37jry57fa.fsf@zoo.weinigel.se> (raw)
In-Reply-To: <4121A689.8030708@bio.ifi.lmu.de>
Frank Steiner <fsteiner-mail@bio.ifi.lmu.de> writes:
> So what's the target in this process? Should users finally be able to
> write cds again without or only with suid bit set? It would be good to
> know if I should try to set all cd writing applications suid or just
> have to wait for some patches coming up that would allow users to
> write cds without suid again...
As far as I can tell the goal is:
With read permissions on the device you should be able to read
from the device, such as ripping from a CD. So all known commands
that don't change the state of the CD should be ok.
With write permissions you should be able to write to media, for
example write to a tape or blank and burn a CDRW.
For all unknown commands you need CAP_SYS_RAWIO (which for most
system means root permissions). So reflashing the firmware of a
CD needs root permissions.
Some commands are a bit questionable though, for example, should it be
possible to use GPCMD_PREVENT_ALLOW_MEDIUM_REMOVAL with only read
permissions?
The MODE_SELECT command I belive is needed for read on some tape
drives because tape parameters such as compression and tape density
are configured this way. But there might be a device where a
MODE_SELECT on a vendor configuration page might destroy the device,
so it might not be such a good idea to allow MODE_SELECT and in that
case I don't know how it should be handled.
Hopefully all commands needed for CD/DVD reading and writing are safe
enough to be allowed with just read or write permission.
/Christer
--
"Just how much can I get away with and still go to heaven?"
Freelance consultant specializing in device driver programming for Linux
Christer Weinigel <christer@weinigel.se> http://www.weinigel.se
next prev parent reply other threads:[~2004-08-17 11:30 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-15 21:43 2.6.8.1 Mis-detect CRDW as CDROM John Wendel
2004-08-15 20:53 ` Alan Cox
2004-08-15 23:24 ` John Wendel
2004-08-15 23:10 ` Alan Cox
2004-08-16 12:38 ` Marc Ballarin
2004-08-16 13:03 ` Alan Cox
2004-08-16 14:58 ` Frank Steiner
2004-08-16 17:44 ` Kronos
2004-08-16 17:57 ` Marc Ballarin
2004-08-16 19:09 ` Marc Ballarin
2004-08-16 19:33 ` Kai Makisara
2004-08-16 21:12 ` Marc Ballarin
2004-08-17 6:32 ` Frank Steiner
2004-08-17 11:11 ` Andreas Messer
2004-08-17 15:59 ` [PATCH] " Andreas Messer
2004-08-17 17:27 ` [RFC] list of SCSI commands Marc Ballarin
2004-08-17 17:56 ` Andreas Messer
2004-08-17 19:43 ` [PATCH] 2.6.8.1 Mis-detect CRDW as CDROM Martin Schlemmer
2004-08-18 8:47 ` Frank Steiner
2004-08-18 9:09 ` Frank Steiner
2004-08-18 9:50 ` [RFC] New security model for scsi_cmd_ioctl Andreas Messer
2004-08-18 12:01 ` [PATCH] 2.6.8.1 Mis-detect CRDW as CDROM Frank Steiner
2004-08-18 12:20 ` Marc Ballarin
2004-08-18 12:27 ` Frank Steiner
2004-08-18 14:08 ` Frank Steiner
2004-08-17 11:29 ` Christer Weinigel [this message]
2004-08-17 11:59 ` Christer Weinigel
2004-08-17 13:25 ` Marc Ballarin
2004-08-17 11:41 ` Marc Ballarin
2004-08-17 13:03 ` Petri Kaukasoina
2004-08-17 14:27 ` [PATCH] update defines in cdrom.h Marc Ballarin
2004-08-17 15:19 ` [PATCH] update + fix " Marc Ballarin
2004-08-16 13:32 ` 2.6.8.1 Mis-detect CRDW as CDROM Petri Kaukasoina
-- strict thread matches above, loose matches on Subject: below --
2004-08-16 7:40 Wolfgang Scheicher
2004-08-16 15:17 ` Adam Jones
[not found] <2tB3a-7rU-19@gated-at.bofh.it>
[not found] ` <2tOWp-cF-5@gated-at.bofh.it>
[not found] ` <2tQlC-1kl-27@gated-at.bofh.it>
2004-08-16 15:06 ` Wolfgang Scheicher
2004-08-16 15:10 ` Frank Steiner
2004-08-16 15:33 Giacomo Perale
2004-08-17 11:14 Joerg Schilling
2004-08-17 11:47 ` Andreas Messer
2004-08-17 13:12 Joerg Schilling
2004-08-17 13:48 ` Andreas Messer
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=m37jry57fa.fsf@zoo.weinigel.se \
--to=christer@weinigel.se \
--cc=Ballarin.Marc@gmx.de \
--cc=Kai.Makisara@kolumbus.fi \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=fsteiner-mail@bio.ifi.lmu.de \
--cc=jwendel10@comcast.net \
--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.