Bug 1263829 - Typo in macros.scl-filesystem creates symlink to wrong location
Typo in macros.scl-filesystem creates symlink to wrong location
Status: CLOSED WONTFIX
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: scl-utils (Show other bugs)
6.6
Unspecified Unspecified
unspecified Severity unspecified
: rc
: ---
Assigned To: packaging-team-maint
BaseOS QE - Apps
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2015-09-16 16:07 EDT by David Walluck
Modified: 2017-12-06 05:53 EST (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2017-12-06 05:53:34 EST
Type: Bug
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 David Walluck 2015-09-16 16:07:42 EDT
There is a typo on line 274 of macros.scl-filesystem from scl-utils version 20120927 which affects all RHEL versions 6.4 through 6.8:

ln -snf ${_localstatedir}/tmp usr/tmp

Note the use of '$' instead of '%'. The variable ${_localstatedir} evaluates to empty causing a symlink to be created from /tmp instead of under the SCL root.

I also question whether all of the flags to the link command are necessary, particularly the force flag as it allows for creating invalid symlinks which will not be caught at build time (in this particular case, /tmp is still a valid path). These flags are used in all RHEL versions 5 through 7.
Comment 2 David Walluck 2015-09-16 16:44:44 EDT
(In reply to David Walluck from comment #0)
> I also question whether all of the flags to the link command are necessary,
> particularly the force flag as it allows for creating invalid symlinks which
> will not be caught at build time (in this particular case, /tmp is still a
> valid path). These flags are used in all RHEL versions 5 through 7.

I see that RHEL 6.3 and below uses a relative symlink which is why these versions are not affected. However, using relative paths and macros like %{_localstatedir} at the same time may not be trivial.
Comment 4 Jan Kurik 2017-12-06 05:53:34 EST
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.