[Pkg-sysvinit-devel] Bug#560222: insserv: How to disable a service permanently?

[Andreas Berger]

the bug still exists in stable (version 1.14.0-2) and from what i remember 
also in testing.

steps to reproduce:

1) insserv -r service
2) aptitude full-upgrade
result: service is running again if the service was in the upgrade


may i propose this be more than wishlist:

for one, the expected behavior is that package upgrades do not override user-
made system configurations without asking (this is the case at least when 
dealing with config files from what i've seen). disabling a service with 
insserv is, from a user view, just as much part of a system configuration as 
editing some .conf file, hence should be respected just as much.

second, the practical implication is a minor security risk imo: after reading 
some article about a samba vulnerability, i did 'pgrep smb' on my playground 
'server' and was very surprised to find samba running, because i remembered 
having disabled it and did not think i would have to re-disable it at any 
time.

i guess the problem is that aptitude automatically makes insserv enable the 
service, regardless of previous state.


regards,
andreas
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 490 bytes
Desc: This is a digitally signed message part.
URL: <http://lists.alioth.debian.org/pipermail/pkg-sysvinit-devel/attachments/20120413/a8c580c5/attachment.pgp>