Bug 178427 - rpm appears to lack means to restore incorrect filemodes
Summary: rpm appears to lack means to restore incorrect filemodes
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: rpm   
(Show other bugs)
Version: 4
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Paul Nasrat
QA Contact: Mike McLean
URL: http://answers.google.com/answers/thr...
Whiteboard:
Keywords: FutureFeature
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2006-01-20 14:58 UTC by Peter Allan
Modified: 2007-11-30 22:11 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2006-01-20 19:25:40 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)

Description Peter Allan 2006-01-20 14:58:50 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8b2) Gecko/20050517 Firefox/1.0+

Description of problem:
I propose a new /usr/bin/rpmfixmodes that will return all or a selection of files (chosen by filename or package) to the values in the RPM DB thus returning to conformity with rpmverify.

I have a quick draft script at
http://www.notatla.org.uk/SOFTWARE/linux_filemode_recovery.txt
but withot the file selection logic.

A dry run reporting planned actions would also be desirable.

If there is interest in including such a tool I'm happy do develop it (in Perl) and contribute it under GPL.


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


How reproducible:
Always

Steps to Reproduce:
1. chmod -R 777 /
2. echo Oh Bother
3.
  

Actual Results:  filemodes are now wrong

Expected Results:  as expected - you asked for it; you got it

Additional info:

Comment 1 Nalin Dahyabhai 2006-01-20 18:35:20 UTC
How does this differ from RPM's "--setperms" and/or "--setugids" options?

Comment 2 Jeff Johnson 2006-01-20 19:25:40 UTC
Doesn't differ at all.


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