Bug 61537
Summary: | Permissions problem with /etc/sysconfig/rhn/up2date.rpmnew | ||
---|---|---|---|
Product: | [Retired] Red Hat Linux | Reporter: | Need Real Name <jms> |
Component: | rpm | Assignee: | Jeff Johnson <jbj> |
Status: | CLOSED NOTABUG | QA Contact: | Jay Turner <jturner> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 7.2 | CC: | gafton, mihai.ibanescu, srevivo |
Target Milestone: | --- | Keywords: | Security |
Target Release: | --- | ||
Hardware: | i386 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2002-12-28 14:12:42 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
Need Real Name
2002-03-21 06:06:52 UTC
up2date is mainly 600 because it could possibly contain proxy user/pass info. But since the standard up2date config doesnt include this, it should be okay. of course, this sounds like a potential rpm bug, so reassigning there. Permissions on *.rpmnew don't matter a bit, as the file can be extracted from the package payload using any convenient means where file permissions are meaningless. Note that the permissions are 600 because the file may be locally modified. |