Bug 210562 - CUPS doesn't work in MLS Enforcing mode
Summary: CUPS doesn't work in MLS Enforcing mode
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: cups
Version: 5.0
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
: ---
Assignee: Tim Waugh
QA Contact: David Lawrence
URL:
Whiteboard:
Depends On:
Blocks: 199636
TreeView+ depends on / blocked
 
Reported: 2006-10-12 21:12 UTC by Irina Boverman
Modified: 2007-11-30 22:07 UTC (History)
0 users

Fixed In Version: beta2
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2006-12-23 01:18:17 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Irina Boverman 2006-10-12 21:12:00 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.0.7) Gecko/20060911 Red Hat/1.5.0.7-0.1.el4 Firefox/1.5.0.7 pango-text

Description of problem:
Description of problem:
The current CUPS code attempts to set the spool files to a ranged MLS label,
which is not allowed in Enforcing mode

Version-Release number of selected component (if applicable):
1.2.4-9

How reproducible:
Every Time.

Please update to the attached patch, which sets the spool files to the
sensitivity level of the client's context. 

See defect 210542 (and attached patch).

This problem should be resolved before rc1.

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


How reproducible:
Always


Steps to Reproduce:
1.see original bug.
2.
3.

Actual Results:
see original bug.

Expected Results:


Additional info:

Comment 1 Irina Boverman 2006-10-12 21:13:56 UTC
Should be fixed in RHEL 5 as well as FC.

Comment 2 Tim Waugh 2006-10-17 10:34:39 UTC
Fixed in cups-1.2.4-9.1.

Comment 4 RHEL Program Management 2006-12-23 01:18:17 UTC
A package has been built which should help the problem described in 
this bug report. This report is therefore being closed with a resolution 
of CURRENTRELEASE. You may reopen this bug report if the solution does 
not work for you.



Note You need to log in before you can comment on or make changes to this bug.