On Tue, Sep 07, 2021 at 12:52:01PM +0000, Peter Stuge <peter@xxxxxxxx> wrote: > 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 Perhaps, when explicitly doing forwarding, you could add "-o ControlMaster=no" to the command line (or alias or script). If I understand correctly, that should work now, without any changes to ssh. cheers, raf _______________________________________________ openssh-unix-dev mailing list openssh-unix-dev@xxxxxxxxxxx https://lists.mindrot.org/mailman/listinfo/openssh-unix-dev
