Red Hat Bugzilla – Bug 1288586
ebtables systemd init script wrong permissions
Last modified: 2016-11-07 06:16:36 EST
Description of problem:
ebtables systemd init script has the executable bits set from the RPM. Systemd complains profusely about this in syslog.
Version-Release number of selected component (if applicable):
# rpm -qi ebtables
Name : ebtables
Version : 2.0.10
Release : 13.el7
Install Date: Fri 04 Dec 2015 08:15:42 AM PST
Group : System Environment/Base
Size : 350432
License : GPLv2+
Signature : RSA/SHA256, Tue 01 Apr 2014 08:01:38 AM PDT, Key ID 199e2f91fd431d51
Source RPM : ebtables-2.0.10-13.el7.src.rpm
Build Date : Tue 04 Mar 2014 04:05:21 AM PST
Build Host : x86-021.build.eng.bos.redhat.com
Relocations : (not relocatable)
Packager : Red Hat, Inc. <http://bugzilla.redhat.com/bugzilla>
Vendor : Red Hat, Inc.
URL : http://ebtables.sourceforge.net/
Summary : Ethernet Bridge frame table administration tool
Ethernet bridge tables is a firewalling tool to transparently filter network
traffic passing a bridge. The filtering possibilities are limited to link
layer filtering and some basic filtering on higher network layers.
This tool is the userspace control for the bridge and ebtables kernel
The ebtables tool can be used together with the other Linux filtering tools,
like iptables. There are no known incompatibility issues.
# rpm -q --dump ebtables | grep systemd
/usr/lib/systemd/system/ebtables.service 208 1393934573 b95ca5c1ab8f8be1946d290a680d3aae5a2037b003841b461a88fdaf1f19013d 0100755 root root 0 0 0 X
Steps to Reproduce:
1. install ebtables
2. rpm -q --dump ebtables | grep systemd
3. inspect permissions column of output
Hopefully you guys have this fixed in newer versions of RHEL 7, if not, here's the bug.
*** Bug 1311546 has been marked as a duplicate of this bug. ***
*** Bug 1360661 has been marked as a duplicate of this bug. ***
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.
*** Bug 1392237 has been marked as a duplicate of this bug. ***