https://bugzilla.mindrot.org/show_bug.cgi?id=2648
Darren Tucker <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |WONTFIX Status|NEW |RESOLVED --- Comment #3 from Darren Tucker <[email protected]> --- (In reply to DarkTrick from comment #2) > I didn't expect it to be such a complex request. I was expecting > some central ssh-request receiver, that has knowledge of that. There is a central process that receives the connections, but it immediately forks of a new process to handle the connection. That child process has to do quite a bit of protocol work before it finds out what the username is. There's a very limited feedback mechanism between those those processes: a pipe that's closed when the child is either authenticated or the child dies which is used to implement MaxStartups. If you were going to implement this you'd probably extend those to provide more information and provide a go/no go decision to the child, but you'd also have to add a mechanism to catch when the user logs out, keep track of the counts and do option parsing. Thanks for the suggestion, but as I said I don't think it's worth the complexity to implement given that many OSes already implement something like it. -- You are receiving this mail because: You are watching the assignee of the bug. You are watching someone on the CC list of the bug. _______________________________________________ openssh-bugs mailing list [email protected] https://lists.mindrot.org/mailman/listinfo/openssh-bugs
