Bug 187268 - permissions on TLS_LICENSE should be 0644, not 0755
permissions on TLS_LICENSE should be 0644, not 0755
Product: Fedora
Classification: Fedora
Component: postfix (Show other bugs)
All Linux
medium Severity low
: ---
: ---
Assigned To: Thomas Woerner
Depends On:
  Show dependency treegraph
Reported: 2006-03-29 12:48 EST by Andrew J. Schorr
Modified: 2007-11-30 17:11 EST (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2007-07-24 09:12:21 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
Fix the file attributes for %{postfix_config_dir}/TLS_LICENSE (654 bytes, patch)
2006-03-29 12:48 EST, Andrew J. Schorr
no flags Details | Diff

  None (edit)
Description Andrew J. Schorr 2006-03-29 12:48:23 EST
Description of problem: postfix.spec file has wrong file
permissions for %{postfix_config_dir}/TLS_LICENSE (should
be 0644, not 0755).

Version-Release number of selected component (if applicable):

How reproducible: When you verify the rpm (rpm --verify postfix),
it complains that the mode is incorrect on /etc/postfix/TLS_LICENSE:

.M......    /etc/postfix/TLS_LICENSE

Steps to Reproduce:
1. rpm --verify postfix
2. ls -l /etc/postfix/TLS_LICENSE
Actual results:

Expected results:

Additional info:
Comment 1 Andrew J. Schorr 2006-03-29 12:48:23 EST
Created attachment 127007 [details]
Fix the file attributes for %{postfix_config_dir}/TLS_LICENSE
Comment 2 Curtis Doty 2006-08-01 22:02:17 EDT
This is such an easy fix. Why has it not shown up in rawhide in over 4 months?

# rpm -V postfix
.M......    /etc/postfix/TLS_LICENSE

Of course postfix will fix your bug upon install. But please make the packaged
perms match what the postfix author intends.

# grep TLS_LICENSE /etc/postfix/postfix-files
Comment 3 Thomas Woerner 2007-07-24 09:12:21 EDT
Fixed in devel in package postfix-2.3.3-1 or newer.

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