Bug 1913693

Summary: Not strict restrictive permissions in the doc folders: perl-devel
Product: Red Hat Enterprise Linux 8 Reporter: Petr Pisar <ppisar>
Component: perlAssignee: perl-maint-list
Status: CLOSED ERRATA QA Contact: Martin Kyral <mkyral>
Severity: low Docs Contact:
Priority: unspecified    
Version: 8.3CC: dvolkov, jorton, jplesnik, mkyral, perl-maint-list, ppisar
Target Milestone: rcKeywords: EasyFix, Patch, Triaged
Target Release: 8.4   
Hardware: Unspecified   
OS: Linux   
Fixed In Version: perl-5.26.3-419.el8 Doc Type: No Doc Update
Doc Text:
Story Points: ---
Clone Of: 1806523 Environment:
Last Closed: 2021-05-18 15:06:02 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:

Description Petr Pisar 2021-01-07 11:55:31 UTC
+++ This bug was initially created as a clone of Bug #1806523 +++

Description of problem:
Files in documentation folder have 'loose' permissions:
    In the file /usr/share/doc/perl-devel-5.16.3/perl-example.stp , the permission is 0664. 0755 is expected or more restrictive

--- Additional comment from Petr Pisar on 2020-02-24 13:14:58 GMT ---

This bug is caused by a 0002 umask on the build server. A simple fix is needed to the specification file:

 #copy the example script
-cp -a %{SOURCE5} .
+install -m 0644 %{SOURCE5} .


--- Additional comment from Petr Pisar on 2020-02-24 16:06:45 GMT ---

While the fix is not applied to RHEL-8 perl, the bug does not manifests there. Probably due to a different Brew code or a configuration.


It manifests in RHEL-8.4.0 scratch builds now.

Comment 6 errata-xmlrpc 2021-05-18 15:06:02 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 (Moderate: perl security and bug fix update), and where to find the updated
files, follow the link below.

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