Bug 166699
Summary: | squirrelmail update screwed permissions | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Dan Hollis <goemon> |
Component: | squirrelmail | Assignee: | Warren Togami <wtogami> |
Status: | CLOSED CANTFIX | QA Contact: | |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 3 | CC: | wtogami |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2005-08-26 02:01:16 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Dan Hollis
2005-08-24 18:36:26 UTC
What is the exact package version of the older version? squirrelmail-1.4.4-1.FC3 actually i see what the problem is. we run apache with a different user/group, so ownership/permissions on /etc/squirrelmail/default_pref had to be different for apache to read it. the upgrade to 1.4.6 stomped the ownership and permissions of /etc/squirrelmail/default_pref. this should not happen as this is a user site specific config file. There is no way of fixing this, and this problem is nothing new with this version of the RPM. Unfortunately you are using it in an unsupported way. Sorry. this is terrifying to anyone using fedora in a production environment, if fedora rpms can stomp permissions of any site-specific configuration file. is there any _clearly stated_ list of fedora 100% supported policies for apache, php and squirrelmail? there doesn't seem to be any documentation on officially supported policies, just 'how to set up apache' with no warnings about policy. man chattr chattr +i <filename> |