All of lore.kernel.org
 help / color / mirror / Atom feed
From: Joerg Schilling <schilling@fokus.fraunhofer.de>
To: schilling@fokus.fraunhofer.de, patrakov@ums.usu.ru
Cc: linux-kernel@vger.kernel.org
Subject: Re: [OT] Joerg Schilling flames Linux on his Blog
Date: Fri, 27 May 2005 12:31:28 +0200	[thread overview]
Message-ID: <4296F700.nail3N024IIC6@burner> (raw)
In-Reply-To: <200505261847.54977.patrakov@ums.usu.ru>

"Alexander E. Patrakov" <patrakov@ums.usu.ru> wrote:

> On Thursday 26 May 2005 16:15, Joerg Schilling wrote:
>
> > The problem was that you could send SCSI commands on R/O fds and fixing the
> > problem would have been to forbid sending SCSI commands on R/O fds.
>
> Unfortunately, this is not going to work. It would work only if the only app 
> that has to send SCSI commands were cdrecord. Then really, a non-setuid 
> program just would not be able to get a R/W fd, and setuid ones are assumed 
> to be trusted.

If these programs did rely on the named security bug, then these programs
were broken anyway and need to be fixed. Note that the _old_ (non ioctl based)
/dev/sg interface needed write access in order to send SCSI commands.


> The problem is that many CD audio players also send SCSI commands in order to 
> extract digital audio data. Are you proposing to make them setuid root? use a 
> well-defined setuid helper? other solution?

If these programs did ever work before, someone did break them meanwhile.


Jörg

-- 
 EMail:joerg@schily.isdn.cs.tu-berlin.de (home) Jörg Schilling D-13353 Berlin
       js@cs.tu-berlin.de		(uni)  
       schilling@fokus.fraunhofer.de	(work) Blog: http://schily.blogspot.com/
 URL:  http://cdrecord.berlios.de/old/private/ ftp://ftp.berlios.de/pub/schily

  reply	other threads:[~2005-05-27 10:33 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-25 13:15 OT] Joerg Schilling flames Linux on his Blog Joerg Schilling
2005-05-25 23:12 ` Kyle Moffett
2005-05-26 10:15   ` Joerg Schilling
2005-05-26 11:42     ` Bill Davidsen
2005-05-26 12:47     ` [OT] " Alexander E. Patrakov
2005-05-27 10:31       ` Joerg Schilling [this message]
     [not found] <4847F-8q-23@gated-at.bofh.it>
2005-05-25 22:46 ` OT] " Joerg Schilling
2005-05-25 23:31   ` Kyle Moffett
2005-05-26  3:45     ` [OT] " Alexander E. Patrakov
2005-05-26  5:06       ` Giuseppe Bilotta
     [not found]       ` <Pine.LNX.4.58.0505261335440.2939@be1.lrz>
2005-05-26 12:33         ` Alexander E. Patrakov
     [not found]           ` <Pine.LNX.4.58.0505261651220.3407@be1.lrz>
2005-05-27 10:44             ` Joerg Schilling
  -- strict thread matches above, loose matches on Subject: below --
2005-05-20 17:45 Patrick McFarland
2005-05-20 17:02 ` jmerkey
2005-05-20 18:24 ` Markus Plail
2005-05-20 18:34 ` Matthias-Christian Ott
2005-05-20 18:41   ` Lee Revell
2005-05-20 23:20 ` Brian O'Mahoney
2005-05-21  7:38   ` Adrian Bunk
2005-05-21 11:25     ` Bernd Petrovitsch
2005-05-21 11:33       ` Måns Rullgård
2005-05-22 18:24         ` Bernd Petrovitsch
2005-05-21 11:41       ` André Tomt
2005-05-21 23:24         ` Adrian Bunk
2005-05-22  0:27           ` Andre Tomt
2005-05-22 14:17             ` Matthias Andree
2005-05-21 16:39     ` Brian O'Mahoney
2005-05-21 23:59       ` Adrian Bunk
2005-05-22  1:22 ` Andrew Haninger
2005-05-22  4:50   ` Patrick McFarland
2005-05-22 14:39     ` Matthias Andree
2005-05-22 20:40     ` Bernhard Rosenkraenzer
2005-05-22 15:54   ` Alistair John Strachan
2005-05-23 13:17 ` Nix
2005-05-23 14:35   ` Brian O'Mahoney
2005-05-23 14:58     ` Nix

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=4296F700.nail3N024IIC6@burner \
    --to=schilling@fokus.fraunhofer.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=patrakov@ums.usu.ru \
    /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.