Bug 160516 - selinux-policy-targeted-1.17.30-2.88 rpm (update) overwrites changes
selinux-policy-targeted-1.17.30-2.88 rpm (update) overwrites changes
Status: CLOSED NOTABUG
Product: Red Hat Enterprise Linux 4
Classification: Red Hat
Component: selinux-policy-targeted (Show other bugs)
4.0
All Linux
medium Severity medium
: ---
: ---
Assigned To: Daniel Walsh
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2005-06-15 11:28 EDT by Richard L. Goerwitz III
Modified: 2007-11-30 17:07 EST (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2005-06-15 14:36:08 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 Richard L. Goerwitz III 2005-06-15 11:28:28 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.6) Gecko/20050328 Fedora/1.7.6-1.2.5

Description of problem:
After installing selinux-policy-targeted-sources, them modifying the squid.te file there to allow squid to bind to port 80 (for use as an accelerator) and to access certain directories it needs to access, I did a 'make', a 'make install' and a 'make load' in the /etc/selinux/targeted/src/policy directory.

When the next RPM update to selinux-policy-targeted and selinux-policy-targeted-sources came along I found my changes overwritten.

Most of the files in the /etc/selinux/targeted/src should be considered configuration files, should they not?

Something similar probably applies to the deployed binary files as well.

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


How reproducible:
Always

Steps to Reproduce:
1. install selinux-policy-targeted-sources
2. make changes to the .te file of your choice; then make, make install, make load
3. install RPM updates and watch your changes get overwritten/inactivated
  

Actual Results:  Squid stopped working (because Selinux reverted to its base/default installation setup).

Expected Results:  My changes should have been left intact.  Basically, some mechanism has to exist that allows binary selinux files to get rebuilt if they source package they depend on is installed and the source files have been changed and deployed.

Additional info:

This will be hard to get right.
Comment 1 Daniel Walsh 2005-06-15 14:36:08 EDT
Changes should get made to your own te files, not one of the standard ones.  So
if you want to make squid changes, create a file domains/misc/local.te and put
your changes their.

Dan

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