On Sat, Jul 23, 2016 at 01:35:04AM +0200, Michael Biebl wrote: > the addition of ssh-session-cleanup.service in the latest upload [1] is > imho a bad idea. It's an aweful hack and besides, it also kills your SSH > sessions on upgrades (thus severity RC). > > The proper fix is to use libpam-systemd. This will register a proper > session scope when users log in via SSH. Those session scopes are > ordered against systemd-user-sessions.service which itself has a proper > ordering against network.target. So those user session are stopped > before the network stack is shutdown. > > Please drop ssh-session-cleanup.service again and simply add a > dependency on libpam-systemd. It's the correct solution for this > problem.
While of course I have libpam-systemd installed on all my systems, I really don't want to depend on it; besides, the original report had people saying that they encountered occasional problems of sessions not being cleaned up even with PAM configured and libpam-systemd installed too. I think I'll add a Recommends on it, but I really want openssh-server to be usable on very minimal systems, including those using other init systems, without having to deal with dependency strangenesses. I didn't notice the session-killing on upgrade *from* this version though. Sigh. Will fix that, thanks! -- Colin Watson [cjwat...@debian.org]
