Support systemd socket activation for sshd about ansible-collection-hardening HOT 2 OPEN

I don't want to include any Debian specific systemd things here. Aside, letting the start AND the listen-port get handled by systemd thus breaking decades old standards seems to much complication for too little benefit. Right now the sshd-hardening-role is very leightweight and I'd like to keep it that way.

So let's rever the behaviour. According to the link you provided we need to do this:

    rm /etc/systemd/system/ssh.service.d/00-socket.conf
    systemctl disable --now ssh.socket
    systemctl enable --now ssh.service
    systemctl daemon-reload
    systemctl restart ssh

In ansible-terms - a task to dlete the 00-socket.conf, disable the ssh.socket, enable the ssh.service. Restart via handler.

@schurzi, what do you think?

from ansible-collection-hardening.

I too think that is the sensible thing to do here. I am just musing over the order of systemctl disable --now ssh.socket and systemctl enable --now ssh.service we should not create situations where ssh access becomes unavailable

from ansible-collection-hardening.