Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Bug 1158759

Summary: Wrong permission for configuration file /etc/sysconfig/virt-who on rhel7.1
Product: Red Hat Enterprise Linux 7 Reporter: Liushihui <shihliu>
Component: virt-whoAssignee: Radek Novacek <rnovacek>
Status: CLOSED ERRATA QA Contact: Li Bin Liu <liliu>
Severity: high Docs Contact:
Priority: unspecified    
Version: 7.1CC: gxing, liliu, ovasik, sgao
Target Milestone: rc   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: virt-who-0.11-3.el7 Doc Type: Bug Fix
Doc Text:
Cause: Configuration file /etc/sysconfig/virt-who was world-readable. Consequence: Any user on the system might read passwords from the configuration file. Fix: Remove read permission for others from the file. Result: File is now only readable by root user. This affects only new deployments. For current deployments, it is advised to set the rights to 600 for /etc/sysconfig/virt-who file.
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-03-05 10:23:26 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1088732    

Description Liushihui 2014-10-30 07:28:53 UTC
Description of problem:
Configuration file /etc/sysconfig/virt-who may contain passwords but its permissions are 644 (rw-r--r--). It should be 600 (rw-------) to prevent non-root users to read the configuration file.

Version-Release number of selected component (if applicable):
virt-who-0.11-2.el7.noarch

How reproducible:
Always

Steps to Reproduce:
1.Check the permission of virt-who config file.
[root@hp-z220-03 20141030094255]# ll /etc/sysconfig/virt-who 
-rw-r--r--. 1 root root 1976 Oct 30 11:18 /etc/sysconfig/virt-who

Actual results:
its permissions are 644 (rw-r--r--)

Expected results:
It should be 600 (rw-------) to prevent non-root users to read the configuration file.

Additional info:

Comment 2 Radek Novacek 2014-11-05 11:55:58 UTC
Fixed in virt-who-0.11-3.el7.

Comment 4 Liushihui 2014-11-12 08:42:27 UTC
Verified it on virt-who-0.11-3.el7.noarch.

Steps to verify:
1.Check the permission of virt-who config file. it's 600 (rw-------)
 [root@hp-z220-06 sysconfig]# ls -alt virt-who
-rw-------. 1 root root 1977 Nov 12 14:57 virt-who

Comment 6 errata-xmlrpc 2015-03-05 10:23:26 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://rhn.redhat.com/errata/RHSA-2015-0430.html