Bug 123365

Summary: k3b needs to run cdrecord with root privileges
Product: [Fedora] Fedora Reporter: Stefan Schwandter <schwandter+bugs>
Component: k3bAssignee: Bill Nottingham <notting>
Status: CLOSED WONTFIX QA Contact:
Severity: medium Docs Contact:
Priority: medium    
Version: rawhideCC: 64bit_fedora, rvokal
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2004-05-24 20:32:04 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Stefan Schwandter 2004-05-17 18:18:40 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6)
Gecko/20040510 Epiphany/1.2.4

Description of problem:
I think the default behaviour of xcdroast in fedora (that it's run as
root by default) has a reason: cdrecord needs to be run as root to
give as much protection against buffer underruns as possible. AFAIK
that's because it needs to be able to set realtime scheduling priority.

The k3b package that's in rawhide now doesn't even have k3bsetup which
could make cdrecord setuid root automatically.

Maybe k3b should be run as root by consolehelper?

Version-Release number of selected component (if applicable):
k3b-0.11.9-3

How reproducible:
Sometimes

Steps to Reproduce:
1. Burn a CDR with k3b
2. Heavy disc access (I installed kdebase with yum, for example) can
cause a buffer underrun
    

Additional info:

Comment 1 Bill Nottingham 2004-05-24 20:32:04 UTC
No; doing so can lead to security holes and increases in update
frequency, which is more work all around.