[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#859693: sysv-rc-conf: disabling auto-start of a systemd service appears successful but is not



Package: sysv-rc-conf
Version: 0.99-7
Severity: important

Dear Maintainer,

*** Reporter, please consider answering these questions, where appropriate ***

   * What led up to the situation?
   * What exactly did you do (or not do) that was effective (or
     ineffective)?
   * What was the outcome of this action?
   * What outcome did you expect instead?

*** End of the template - remove these template lines ***

Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: user <user@localhost.localdomain>
To: Debian Bug Tracking System <submit@bugs.debian.org>
Subject: sysv-rc-conf: disabling a systemd service appears to work but the service
 still runs
Message-ID: <20170406034251.3634.68427.reportbug@computer>
X-Mailer: reportbug 6.6.3
Date: Wed, 05 Apr 2017 20:42:51 -0700
X-Debbugs-Cc: user@localhost.localdomain

Package: sysv-rc-conf
Version: 0.99-7
Severity: important

Dear Maintainer,

I have lighttpd and sysv-rc-conf installed from the standard Jessie (currently
Stable) repos.

For security and other reasons, I used sysv-rc-conf to disable auto-starting of
lighttpd and some other services. The program's console UI "properly" cleared
the auto-start boxes for lighttpd (and other services) in all runlevels and
exited normally. Upon rebooting, I was very upset to learn that lighttpd had
auto-started anyway (seen with "service lighttpd status" which shows it as
executing with /lib/systemd/system/lighttpd.service ).

Other services, those which start from /etc/init.d/* seem to respond correctly,
though.

Note that this is a real-world impact of related bug #791689

If users are led to believe that a service has been disabled when it is in fact
still running, the consequences could be serious from a security perspective,
not to mention that if updates are made to the unit files themselves, major
conflicts could emerge from duplicate services and so on.

Thank you very much.

-- System Information:
Debian Release: 8.7
  APT prefers stable
  APT policy: (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages sysv-rc-conf depends on:
ii  libcurses-ui-perl  0.9609-1
ii  sysv-rc            2.88dsf-59

sysv-rc-conf recommends no packages.

sysv-rc-conf suggests no packages.

-- no debconf information

-- System Information:
Debian Release: 8.7
  APT prefers stable
  APT policy: (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages sysv-rc-conf depends on:
ii  libcurses-ui-perl  0.9609-1
ii  sysv-rc            2.88dsf-59

sysv-rc-conf recommends no packages.

sysv-rc-conf suggests no packages.

-- no debconf information


Reply to: