On Mon, May 02, 2016 at 05:44:31PM -0000, Colin Watson wrote: > I'm not sure how that would make any difference at all. The problem is > that it's hard for sshd to maintain the necessary state across multiple > invocations when it's being invoked once per connection rather than > having a master process that can trivially keep track of all the > inter-connection state it needs.
When using the sd_listen_fds(3) protocol, systemd is *not* calling accept() on the service's behalf, and is not launching per-connection instances of the service. The socket activation is merely lazy initialization, where once a connection comes in, the normal ssh service is launched and manages that socket from there on out. So there would be a master process keeping track, unless I've overlooked something? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1576353 Title: Install openssh-server with disabled password auth by default on servers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-cdimage/+bug/1576353/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
