[Bug 1815] RemoteCommand and PseudoTTY config options
https://bugzilla.mindrot.org/show_bug.cgi?id=1815 Damien Miller changed: What|Removed |Added CC||d...@mindrot.org Status|NEW |RESOLVED Resolution||FIXED --- Comment #1 from Damien Miller 2011-05-20 12:53:01 EST --- OpenSSH 5.9 will have a RequestTTY option, but I don't think we need an option to specify the command -- Configure bugmail: https://bugzilla.mindrot.org/userprefs.cgi?tab=email --- 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 1815] RemoteCommand and PseudoTTY config options
https://bugzilla.mindrot.org/show_bug.cgi?id=1815 Björn "Vampire" Kautler changed: What|Removed |Added Status|RESOLVED|REOPENED Resolution|FIXED | --- Comment #2 from Björn "Vampire" Kautler 2011-05-21 02:37:10 EST --- May I ask why not? This possibility proved to be veeery useful to me. I'm doing things like the following with it: config: Host wbl RemoteCommand wakeonlan -f wol/bjkau-linux.wol command to wake up my box remotely: ssh wbl config: Host v2bl User root LocalForward 5900 localhost:5900 RemoteCommand x11vnc -localhost -timeout 120 -display :0 -auth /var/lib/gdm/:0.Xauth command to start a secure remote x11vnc session: ssh v2bl vinagre localhost (or invoked via GUI) config which would be possible without RemoteCommand but very ugly like shown in the initial comment: Host sf* shell.sf.net shell.sourceforge.net HostName shell.sourceforge.net RequestTTY yes RemoteCommand create command to connect to SF Shell service: ssh sfj I would really miss this feature if it doesn't get added and always building an own version with my patch is cumbersome. :-( I'd really appreciate if this also gets added like suggested. -- Configure bugmail: https://bugzilla.mindrot.org/userprefs.cgi?tab=email --- 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 1815] RemoteCommand and PseudoTTY config options
https://bugzilla.mindrot.org/show_bug.cgi?id=1815 Bert Wesarg changed: What|Removed |Added CC||bert.wes...@googlemail.com --- Comment #3 from Bert Wesarg 2011-05-22 04:07:30 EST --- (In reply to comment #2) > May I ask why not? My personal opinion would be that this is a job for a script. And note that this is even shorter to type: > config: > > Host v2bl > User root > LocalForward 5900 localhost:5900 > RemoteCommand x11vnc -localhost -timeout 120 -display :0 -auth > /var/lib/gdm/:0.Xauth > > command to start a secure remote x11vnc session: > > ssh v2bl v2bl.sh: #!/bin/sh exec ssh v2bl -t x11vnc -localhost -timeout 120 -display :0 -auth > /var/lib/gdm/:0.Xauth command: v2bl.sh -- Configure bugmail: https://bugzilla.mindrot.org/userprefs.cgi?tab=email --- 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 1815] RemoteCommand and PseudoTTY config options
https://bugzilla.mindrot.org/show_bug.cgi?id=1815 --- Comment #4 from Björn "Vampire" Kautler 2011-05-22 09:35:11 EST --- Of course as script or alias it is shorter to type. But I like to have this configuration there. And those also were only examples, there are for sure other use-cases. And hey, if someone doesn't want to use the feature he doesn't have to and can still use scripts or aliases. :-) While neither scripts nor aliases are portable. The ssh config file I can also copy over to a Windows machine running openssh and can immediately use it. Aliases are not possible on Windoze and a script would have to be rewritten as BAT script. Besides that especially the SourceForge case does belong in that config file logically as that "create" command is necessary to establish an SSH connection to the SourceForge shell service. That is why it was my example in the initial description. -- Configure bugmail: https://bugzilla.mindrot.org/userprefs.cgi?tab=email --- 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 1815] RemoteCommand and PseudoTTY config options
https://bugzilla.mindrot.org/show_bug.cgi?id=1815 Tisza Gergő changed: What|Removed |Added CC||gti...@gmail.com --- Comment #5 from Tisza Gergő --- One possible use case for RemoteCommand would be to set different prompts on certain machines (e.g. if we SSH to the production server, change the prompt to red). This could be done via sshrc, but that might be inconvenient or controversial if the remote account is used by many different people. -- 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 1815] RemoteCommand and PseudoTTY config options
https://bugzilla.mindrot.org/show_bug.cgi?id=1815 Darren Tucker changed: What|Removed |Added CC||dtuc...@zip.com.au Status|REOPENED|RESOLVED Resolution|--- |FIXED --- Comment #6 from Darren Tucker --- if you're using openssh on windows you've likely got enough of cygwin to run shell scripts as well. anyway: we're not adding RemoteCommand because it is not needed. there's lots of other ways of achieving the same goal: a local script, remote ForceCommand, remote sshrc, remote shell startup file. -- 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 1815] RemoteCommand and PseudoTTY config options
https://bugzilla.mindrot.org/show_bug.cgi?id=1815 Björn "Vampire" Kautler changed: What|Removed |Added Status|RESOLVED|REOPENED Resolution|FIXED |--- --- Comment #7 from Björn "Vampire" Kautler --- This is not FIXED, at most it is WONTFIX. But I cannot agree with "it is not needed". remote ForceCommand, remote sshrc and remote shell startup file can only support one command per user per host (the first even one command for all users) and also the SourceForge usecase is NOT POSSIBLE with it. local script is possible of course, but you can replace most of the other ssh Options by a local script also with using command-line parameters. And the SourceForge case is also there NOT POSSIBLE when trying to use rsync or scp. -- 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 1815] RemoteCommand and PseudoTTY config options
https://bugzilla.mindrot.org/show_bug.cgi?id=1815 Darren Tucker changed: What|Removed |Added Status|REOPENED|RESOLVED Resolution|--- |FIXED --- Comment #8 from Darren Tucker --- We added RequestTTY, that's why it was marked as fixed. We don't agree with your rationale for the RemoteCommand changes and have decided not to add 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 openssh-bugs@mindrot.org https://lists.mindrot.org/mailman/listinfo/openssh-bugs
[Bug 1815] RemoteCommand and PseudoTTY config options
https://bugzilla.mindrot.org/show_bug.cgi?id=1815 Damien Miller changed: What|Removed |Added Status|RESOLVED|CLOSED --- Comment #9 from Damien Miller --- Close all resolved bugs after 7.3p1 release -- 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