Mailinglist Archive: opensuse (4294 mails)

< Previous Next >
Re: [opensuse] Re: k3bsetup
  • From: "Joe Morris (NTM)" <Joe_Morris@xxxxxxx>
  • Date: Tue, 12 Dec 2006 22:02:14 +0800
  • Message-id: <457EB666.6030806@xxxxxxx>
Joachim Schrod wrote:
> Michal Hlavac wrote:
>> when I start k3b (suse 10.2) it says this:
>> cdrecord will be run without root privileges
>> It is highly recommended to configure cdrecord to run with root
>> privileges. Only then cdrecord runs with high priority which
>> increases the overall stability of the burning process. Apart from
>> that it allows changing the size of the used burning buffer. A lot of
>> user problems could be solved this way. This is also true when using
>> SuSE's resmgr.
>> Solution: Use K3bSetup to solve this problem.
But I know it does work as is, even with the message.
> k3bsetup sets cdrecord setuid-root, doesn't it? How do you prevent
> that it is set back to 755, according to /etc/permissions, when
> SuSEconfig is run the next time? (This is done by the module
> /sbin/conf.d/SuSEconfig.permissions and controlled by
> /etc/sysconfig/security.)
> If cdrecord needs to run with root privileges, it should be installed
> so from the start and not changed by k3bsetup, IMHO. The latter won't
> survive for long in a standard SUSE setup, the setuid bit will
> disappear after the next sysadmin activity that causes SuSEconfig to run.
You are correct, but not only that, but AFAIR, after kernel 2.6.8, it
must NOT be SUID root, because of a security change made in the kernel
at that time. I know I used to set those permissions the SuSE way, in
/etc/permissions.local, but found after 2.6.8 it would not work as
root. I'm not sure of the present state of all that, I've lost track,
but I know I have NOT needed to change the permissions of cdrecord for a
long time, and as long as resmgr is working, it DOES work as is, no
messing needed.

Joe Morris
Registered Linux user 231871

To unsubscribe, e-mail: opensuse+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse+help@xxxxxxxxxxxx

< Previous Next >
Follow Ups