[Bug 1972667] [NEW] Permissions problem on run scripts after networkd-dispatcher (1.7-0ubuntu3.4)
Roger Cornelius
1972667 at bugs.launchpad.net
Mon May 9 14:55:46 UTC 2022
Public bug reported:
I'm unsure if this is a bug or intended behavior. I posted to
answers.launchpad.net but received no helpful replies.
On ubuntu 20.04.4 LTS after install of update “networkd-dispatcher
(1.7-0ubuntu3.4)”, scripts in /etc/networkd-dispatcher/routable.d with
700 permissions that used to run as expected, fail to do so. E.g., I
have some routing commands in /etc/networkd-
dispatcher/routable.d/50-iptables that should execute at boot time but
stopped after this update installed, and ‘service networkd-dispatcher
status’ returns:
May 07 14:14:49 Krieger networkd-dispatcher[581]: ERROR:invalid
permissions on /etc/networkd-dispatcher/routable.d/50-iptables. Expected
mode=0o755, uid=0, gid=0; got mode=0o700, uid=0, >
Changing permissions on 50-iptables from 0700 to 0755 corrected the
problem.
I've read the Changelog for the update, and the later update “networkd-
dispatcher (1.7-0ubuntu3.5)” which corrected a regression has also been
applied but the unexpected behavior remains.
Is this less-restrictive permissions requirement an intended result of
the update? Is the perms requirement documented anywhere? I don't see
it in the networkd-dispatcher man page.
Thank you
** Affects: networkd-dispatcher (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to networkd-dispatcher in Ubuntu.
https://bugs.launchpad.net/bugs/1972667
Title:
Permissions problem on run scripts after networkd-dispatcher
(1.7-0ubuntu3.4)
Status in networkd-dispatcher package in Ubuntu:
New
Bug description:
I'm unsure if this is a bug or intended behavior. I posted to
answers.launchpad.net but received no helpful replies.
On ubuntu 20.04.4 LTS after install of update “networkd-dispatcher
(1.7-0ubuntu3.4)”, scripts in /etc/networkd-dispatcher/routable.d with
700 permissions that used to run as expected, fail to do so. E.g., I
have some routing commands in /etc/networkd-
dispatcher/routable.d/50-iptables that should execute at boot time but
stopped after this update installed, and ‘service networkd-dispatcher
status’ returns:
May 07 14:14:49 Krieger networkd-dispatcher[581]: ERROR:invalid
permissions on /etc/networkd-dispatcher/routable.d/50-iptables.
Expected mode=0o755, uid=0, gid=0; got mode=0o700, uid=0, >
Changing permissions on 50-iptables from 0700 to 0755 corrected the
problem.
I've read the Changelog for the update, and the later update
“networkd-dispatcher (1.7-0ubuntu3.5)” which corrected a regression
has also been applied but the unexpected behavior remains.
Is this less-restrictive permissions requirement an intended result of
the update? Is the perms requirement documented anywhere? I don't
see it in the networkd-dispatcher man page.
Thank you
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/networkd-dispatcher/+bug/1972667/+subscriptions
More information about the foundations-bugs
mailing list