Hi, Philipp Marek wrote: > But the TCP forwards still worked - of course, > as the ControlMaster process was still active! > > What I'd like to ask/discuss is -- perhaps the TCP forwarding should > (optionally, by default) be bound to the interactive SSH process - > and when that one quits, the forwarding is stopped? I'd also like such behavior, but I don't know if the session owner (the Master process) can reliably tell when a Slave process exits? A first step might be to enable Slave processes to not only add but also remove previously established channels? //Peter _______________________________________________ openssh-unix-dev mailing list openssh-unix-dev@xxxxxxxxxxx https://lists.mindrot.org/mailman/listinfo/openssh-unix-dev
