Package: miredo
Version: 1.2.6-7
Severity: serious
Hi,
stopping or restarting miredo on systems with sysvinit (or probably also
any other init system using start-stop-daemon) fails as follows for me:
invoke-rc.d miredo restart
[....] Stopping Teredo IPv6 tunneling daemon: miredostart-stop-daemon: matching
only on non-root pidfile
/var/run/miredo.pid is insecure
failed!
And miredo is indeed not stopped:
root 1225 0.0 0.0 12100 0 ? Ss Jan13 0:00
/usr/sbin/miredo
miredo 1226 0.0 0.0 110556 0 ? Sl Jan13 0:33
/usr/sbin/miredo
root 1228 0.0 0.0 6904 316 ? S Jan13 0:00
/usr/libexec/miredo/miredo-privproc B
This is caused by the following change in dpkg 1.19.3 from 22 Jan 2019:
* start-stop-daemon: Check whether standalone --pidfile use is secure.
Prompted by Michael Orlitzky <mich...@orlitzky.com>.
The usual fix seems to be to also specify the binary to be stopped with
IIRC the --exec option.
-- System Information:
Debian Release: buster/sid
APT prefers unstable
APT policy: (990, 'unstable'), (600, 'testing'), (500, 'unstable-debug'),
(500, 'buildd-unstable'), (110, 'experimental'), (1, 'experimental-debug'), (1,
'buildd-experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 4.18.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE=C.UTF-8
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)
LSM: AppArmor: enabled
Versions of packages miredo depends on:
ii adduser 3.118
ii init-system-helpers 1.56+nmu1
ii iproute2 4.20.0-2
ii libc6 2.28-8
ii libcap2 1:2.25-2
ii libjudydebian1 1.0.5-5
ii lsb-base 10.2018112800
ii makedev 2.3.1-94
ii udev 241-1
miredo recommends no packages.
miredo suggests no packages.
-- no debconf information
