Stop enabling ssh-session-cleanup.service by default; instead, ship it as an example and add a section to README.Debian. libpam-systemd >= 230 and "UsePAM yes" should take care of the original problem for most systemd users (thanks, Michael Biebl; closes: #832155).

1 files changed, 0 insertions, 6 deletions

diff --git a/debian/rules b/debian/rules
index 540418e7b..3a8c86cdc 100755
--- a/debian/rules
+++ b/debian/rules
@@ -215,12 +215,6 @@ override_dh_installdocs:
 override_dh_systemd_enable:
         dh_systemd_enable -popenssh-server --name ssh ssh.service
         dh_systemd_enable -popenssh-server --name ssh --no-enable ssh.socket
-        dh_systemd_enable -popenssh-server --name ssh-session-cleanup \
-                ssh-session-cleanup.service
-
-override_dh_systemd_start:
-        dh_systemd_start -popenssh-server --no-restart-on-upgrade \
-                ssh-session-cleanup.service
 
 override_dh_installinit:
         dh_installinit -R --name ssh