On 2022-10-12 13:52:26 +0200, Michael Biebl wrote: > > Am 12.10.22 um 13:15 schrieb Vincent Lefevre: > > On 2022-10-12 11:39:40 +0200, Michael Biebl wrote: > > > > If you don't want to constantly start/stop the user instance, you can also > > > use linger, so the user instance will stick around if you terminate your > > > SSH > > > session. > > > > However, I suppose that this would take useless resources. IMHO, > > Judging from your log, `systemd --user` basically just set's up listening > sockets. So all you've got is the `systemd --user` process itself + a couple > of open file descriptors. > > Is that really any issue?
Probably not a real issue. However, I think that there should be a way to disable systemd (and perhaps have more control over PAM), e.g. with an authorized_keys option as I've just suggested, as this is precisely where one can require a limited use of ssh. Perhaps this bug could be reassigned to openssh-server (this package also provides /etc/pam.d/sshd, so it is also concerned by the PAM configuration). -- Vincent Lefèvre <vinc...@vinc17.net> - Web: <https://www.vinc17.net/> 100% accessible validated (X)HTML - Blog: <https://www.vinc17.net/blog/> Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)
