[Bug 3456] provide a way to have forwardings killed, when the remote command/shell finishes

2022-07-05 Thread bugzilla-daemon
https://bugzilla.mindrot.org/show_bug.cgi?id=3456

Darren Tucker  changed:

   What|Removed |Added

 CC||dtuc...@dtucker.net

--- Comment #1 from Darren Tucker  ---
I think you can do what you're describing on the command line,
something like:
$ ssh -L 1234:127.0.0.1:5900 yourserver 'vncserver; kill $PPID'

-- 
You are receiving this mail because:
You are watching someone on the CC list of the bug.
You are watching the assignee of the bug.
___
openssh-bugs mailing list
openssh-bugs@mindrot.org
https://lists.mindrot.org/mailman/listinfo/openssh-bugs


[Bug 3456] provide a way to have forwardings killed, when the remote command/shell finishes

2022-07-05 Thread bugzilla-daemon
https://bugzilla.mindrot.org/show_bug.cgi?id=3456

--- Comment #2 from Christoph Anton Mitterer  ---
I assume your idea here is that this kills the server side ssh process
and thereby also the forwarding, which isn't closed because of
whathever happens between remmina and vnc?

I tried it and while it works in principle it seems rather a hacky
workaround:
- the ssh client gives an error message as the connection is not
cleanly shut down
- exit status becomes 255 and not the one with which the remote command
exits

-- 
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
openssh-bugs@mindrot.org
https://lists.mindrot.org/mailman/listinfo/openssh-bugs


[Bug 3456] provide a way to have forwardings killed, when the remote command/shell finishes

2022-07-06 Thread bugzilla-daemon
https://bugzilla.mindrot.org/show_bug.cgi?id=3456

Damien Miller  changed:

   What|Removed |Added

 CC||d...@mindrot.org

--- Comment #3 from Damien Miller  ---
You could also do this using the multiplexing control socket and -O
cancel

-- 
You are receiving this mail because:
You are watching someone on the CC list of the bug.
You are watching the assignee of the bug.
___
openssh-bugs mailing list
openssh-bugs@mindrot.org
https://lists.mindrot.org/mailman/listinfo/openssh-bugs


[Bug 3456] provide a way to have forwardings killed, when the remote command/shell finishes

2022-07-06 Thread bugzilla-daemon
https://bugzilla.mindrot.org/show_bug.cgi?id=3456

--- Comment #4 from Christoph Anton Mitterer  ---
> You could also do this using the multiplexing control socket and -O cancel

But AFAIU, this I'd need to do on the local side in an extra command.

So when I have some:
$ ssh foo.example.org

which sets up the forwarding and does via RemoteCommand start the
remote service... and that then "hangs" because the forwarding is kept
open even after the RemoteCommand has finished,... I would need to run
the cancel command from somewhere else, i.e. manually.

So that's merely "as good" as manually doing a Ctrl-C.

-- 
You are receiving this mail because:
You are watching someone on the CC list of the bug.
You are watching the assignee of the bug.
___
openssh-bugs mailing list
openssh-bugs@mindrot.org
https://lists.mindrot.org/mailman/listinfo/openssh-bugs


[Bug 3456] provide a way to have forwardings killed, when the remote command/shell finishes

2023-02-09 Thread bugzilla-daemon
https://bugzilla.mindrot.org/show_bug.cgi?id=3456

--- Comment #5 from Damien Miller  ---
AFAIK this would work:

ssh -oControlMaster=auto -oControlPersist=1s \
-oControlPath=/path -L[forward] user@host command ; \
ssh -oControlPath=/path -Oexit user@host

-- 
You are receiving this mail because:
You are watching someone on the CC list of the bug.
You are watching the assignee of the bug.
___
openssh-bugs mailing list
openssh-bugs@mindrot.org
https://lists.mindrot.org/mailman/listinfo/openssh-bugs


[Bug 3456] provide a way to have forwardings killed, when the remote command/shell finishes

2023-04-14 Thread bugzilla-daemon
https://bugzilla.mindrot.org/show_bug.cgi?id=3456

--- Comment #6 from Christoph Anton Mitterer  ---
Thanks Daimen... but still not particularly "user-friendly" in the
sense that one still has to write a special command (2x ssh with
special options) and cannot simply "ssh host" as usual.

Wouldn't it be possible to get a config option that simply decides what
should happen if there are still forwardings while the command has
finished, i.e. either keep them open or close them and thus exit?

-- 
You are receiving this mail because:
You are watching someone on the CC list of the bug.
You are watching the assignee of the bug.
___
openssh-bugs mailing list
openssh-bugs@mindrot.org
https://lists.mindrot.org/mailman/listinfo/openssh-bugs