Bug 855905 - yum-plugin-versionlock may change the permissions of its version-locks file
Summary: yum-plugin-versionlock may change the permissions of its version-locks file
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: yum-utils
Version: 6.3
Hardware: Unspecified
OS: Unspecified
low
low
Target Milestone: rc
: ---
Assignee: Valentina Mukhamedzhanova
QA Contact: BaseOS QE Security Team
URL:
Whiteboard:
Depends On:
Blocks: 1499211
TreeView+ depends on / blocked
 
Reported: 2012-09-10 15:03 UTC by Gianni Giardina
Modified: 2017-12-06 10:39 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-12-06 10:39:33 UTC
Target Upstream Version:


Attachments (Terms of Use)

Description Gianni Giardina 2012-09-10 15:03:22 UTC
Description of problem
----------------------

After removing a version-lock entry with the command:

# yum versionlock delete <entry-wildcard>

it becomes no more possible to run "yum ceck-update" as a normal user. This is because the reading permissions of the versionlock.list file have been removed.


Version-Release number of selected component
--------------------------------------------

yum-3.2.29-30.el6.noarch
yum-plugin-versionlock-1.1.30-14.el6.noarch


Steps to Reproduce
------------------

1. Check the permission of versionlock.list:

# ls -l /etc/yum/pluginconf.d/versionlock.list
-rw-r--r--. 1 root root 36 Sep 10 11:04 /etc/yum/pluginconf.d/versionlock.list

2. Verify that they are the right ones:

# rpm -V yum-plugin-versionlock
S.5....T.  c /etc/yum/pluginconf.d/versionlock.list

3. Remove a version-lock entry:

# yum versionlock delete 0:mdadm-3.2.2-9.el6.*
Loaded plugins: aliases, changelog, downloadonly, fastestmirror, filter-data,
              : list-data, post-transaction-actions, presto, priorities,
              : refresh-packagekit, remove-with-leaves, security, show-leaves,
              : tmprepo, verify, versionlock
Deleting versionlock for: 0:mdadm-3.2.2-9.el6.*

4. Check the permission of versionlock.list again:

# ls -l /etc/yum/pluginconf.d/versionlock.list
-rw-------. 1 root root 36 Sep 10 11:04 /etc/yum/pluginconf.d/versionlock.list

  
Actual results
--------------

If you try to run "yum check-update" as a normal user you get the following error message:

Unable to read version lock configuration: [Errno 14] Could not open/read file:///etc/yum/pluginconf.d/versionlock.list


Expected results
----------------

As a normal user, I should be able to run "yum check-update" as like as most yum "query" commands.


Workaround
----------

# chmod a+r /etc/yum/pluginconf.d/versionlock.list

after any "yum versionlock delete ..." but is annoying.

Comment 2 RHEL Program Management 2012-09-26 15:48:45 UTC
This request was evaluated by Red Hat Product Management for
inclusion in the current release of Red Hat Enterprise Linux.
Because the affected component is not scheduled to be updated
in the current release, Red Hat is unable to address this
request at this time.

Red Hat invites you to ask your support representative to
propose this request, if appropriate, in the next release of
Red Hat Enterprise Linux.

Comment 3 Zdeněk Pavlas 2013-04-19 09:19:36 UTC
commit 5895426f12354ac6ca26de8aea59d200e8fbd26c
Author: Zdeněk Pavlas <zpavlas@redhat.com>
Date:   Mon Sep 24 16:18:08 2012 +0200

    Keep "/etc/yum/pluginconf.d/versionlock.list" user-readable.  BZ 855905

Comment 6 RHEL Program Management 2013-10-14 00:27:56 UTC
This request was evaluated by Red Hat Product Management for
inclusion in the current release of Red Hat Enterprise Linux.
Because the affected component is not scheduled to be updated
in the current release, Red Hat is unable to address this
request at this time.

Red Hat invites you to ask your support representative to
propose this request, if appropriate, in the next release of
Red Hat Enterprise Linux.

Comment 10 Jan Kurik 2017-12-06 10:39:33 UTC
Red Hat Enterprise Linux 6 is in the Production 3 Phase. During the Production 3 Phase, Critical impact Security Advisories (RHSAs) and selected Urgent Priority Bug Fix Advisories (RHBAs) may be released as they become available.

The official life cycle policy can be reviewed here:

http://redhat.com/rhel/lifecycle

This issue does not meet the inclusion criteria for the Production 3 Phase and will be marked as CLOSED/WONTFIX. If this remains a critical requirement, please contact Red Hat Customer Support to request a re-evaluation of the issue, citing a clear business justification. Note that a strong business justification will be required for re-evaluation. Red Hat Customer Support can be contacted via the Red Hat Customer Portal at the following URL:

https://access.redhat.com/


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