On Thu 2016-05-12 09:43:12 -0400, Christoph Anton Mitterer wrote:
> btw: It seems that -8, (in which sks starts again), the service is not
> enabled per default.
>
> I personally think that's good, because I consider Debian's usual
> behaviour of enabling services at installation insecure and stupid, but
> perhaps you may still want to follow that.
the sysvinit approach also doesn't start the service by default. the
admin has to manually edit /etc/default/sks in order to get it to start
up.
With systemd as pid 1, the admin needs instead to:
systemctl enable systemd
This is a superior arrangement (esp. considering that it's not possible
to start up sks without jumping through keydump fetches and db builds),
and I am happy with it. It's all documented in
/usr/share/doc/README.Debian.
--dkg
