Bug 453621 - Odd file permissions in apg
Odd file permissions in apg
Status: CLOSED RAWHIDE
Product: Fedora
Classification: Fedora
Component: apg (Show other bugs)
9
All Linux
low Severity low
: ---
: ---
Assigned To: Kevin Fenzi
Fedora Extras Quality Assurance
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2008-07-01 12:09 EDT by J. Randall Owens
Modified: 2008-08-11 20:30 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2008-08-11 20:30:31 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description J. Randall Owens 2008-07-01 12:09:03 EDT
Description of problem:
I noticed that when listing the contents of my /etc/xinetd.d/ directory, apgd
stands out as the only one with execute permissions set.  Looking at the
contents of the package more, I see the man pages are as well.  All -rwxr-xr-x.
 These should probably be turned off sometime for consistency, though I suppose
it's not worth a release just for the sake of this.

Version-Release number of selected component (if applicable):
apg-2.3.0b-6.fc9

How reproducible:
examine permissions of /etc/xinetd.d/* and the apg man pages

Steps to Reproduce:
1. install apg
2. ls -Z /etc/xinetd.d
3. ls -Z /usr/share/man/man1/apg*.1.gz /usr/share/man/man8/apgd.8.gz
  
Actual results:
-rwxr-xr-x in the apg files, -rw-r--r-- on those not belonging to apg

Expected results:
-rw-r--r-- all the way through

Additional info:
Could be fixed either by adding '-m 0644' to the `install -D...` lines, or
setting '%attr(644,-,-)' on the relevant %files entries.
Comment 1 Kevin Fenzi 2008-08-11 20:30:31 EDT
I have just checked in and built a fix for this in rawhide. 
I agree, it's not worth pushing to stable branches...

Feel free to re-open or file a new bug if you spot anything further. 

Thanks for the report!

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