Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 17 Jun 1997 01:30:02 -0700 (PDT)
From:      Luigi Rizzo <luigi@labinfo.iet.unipi.it>
To:        freebsd-bugs
Subject:   Re: bin/3837: new feature for rtprio
Message-ID:  <199706170830.BAA02883@hub.freebsd.org>

next in thread | raw e-mail | index | archive | help
The following reply was made to PR bin/3837; it has been noted by GNATS.

From: Luigi Rizzo <luigi@labinfo.iet.unipi.it>
To: joerg_wunsch@uriah.heep.sax.de
Cc: luigi@iet.unipi.it, FreeBSD-gnats-submit@FreeBSD.ORG
Subject: Re: bin/3837: new feature for rtprio
Date: Tue, 17 Jun 1997 09:53:12 +0200 (MET DST)

 > As Luigi Rizzo wrote:
 > 
 > > 	This patch allows users listed in /etc/rtprio.conf to set
 > > 	realtime priorities for processes. Useful to let non-root
 > > 	users burn CDs. I also include the small manpage change.
 > 
 > Sorry to take you down on this, but i don't like it.  If we start to
 > create /etc/foo.conf for every foo that requires root privileges, we
 > won't ever come to an end.
 
 agreed. Jordan already pointed this out, and suggested the use of
 login.conf for this (and other similar) capability.
 
 The problem: I have 2.2.1, and don't know what do I need to upgrade in
 order to have login.conf working. "login" perhaps, and then what else ?
 
 > Your problem is exactly what things like suidperl or sudo have been
 > made for.  This has the additional advantage that you don't need to
 > trust some user more than the other, but only need to trust some
 > application to not abuse the feature.
 
 Abstracting from the specific problem, one way or another, if the
 number of apps requiring root privs is large, you'll have a large
 configuration database, be it in the form of foo.conf files, or
 login.conf capabilities, or sudo configuration entries. Methods to
 simplify configurations apply to all the above variants (although
 I agree that my foo.conf idea is the worst of the 3 and let's assume
 I never proposed it :)
 
 Coming to rtprio, the problem is that it does an exec of the next
 program without dropping privileges, so once you have made it run
 with root privs you have lost any security. It really needs to be
 patched, one way or another, to run with root privs.
 
 	Cheers
 	Luigi
 -----------------------------+--------------------------------------
 Luigi Rizzo                  |  Dip. di Ingegneria dell'Informazione
 email: luigi@iet.unipi.it    |  Universita' di Pisa
 tel: +39-50-568533           |  via Diotisalvi 2, 56126 PISA (Italy)
 fax: +39-50-568522           |  http://www.iet.unipi.it/~luigi/
 _____________________________|______________________________________



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199706170830.BAA02883>