Bug 34739 - checkpc has wrong perms for "filter"
Summary: checkpc has wrong perms for "filter"
Status: CLOSED RAWHIDE
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: LPRng   
(Show other bugs)
Version: 7.1
Hardware: i386
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Crutcher Dunnavant
QA Contact: David Lawrence
URL:
Whiteboard:
Keywords:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2001-04-04 17:08 UTC by j. alan eldridge
Modified: 2007-04-18 16:32 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2001-04-04 17:08:50 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description j. alan eldridge 2001-04-04 17:08:47 UTC 
This change occurred with the 3.7.4 RPM used by both wolverine and rawhide.
There's a program called checkpc which, among other things, forces 
permissions for certain files back to values it "knows". 

Well, for /var/spool/lpd/{printer}/filter, a symlink 
to /usr/libexec/master-filter, checkpc wants the perms for this file to be 
0600. Unfortunately, lpd wants (*needs*) the permissions to be 700, since 
it needs to execute that file.

So, when you start lpd, checkpc bitches about perms on .../filter being 
711, not 600, and sets them to 600. Then lpd comes along and bitches that 
the .../filter does not have execute permission.

In this little battle of wills, lpd is right, since if /usr/libexec/master-
filter doesn't have execute perms, nothing gets spooled or printed.
Comment 1 Preston Brown 2001-04-04 20:24:23 UTC 
this has been fixed in at least LPRng-3.7.4-22 and later.
Note You need to log in before you can comment on or make changes to this bug.