Oops. That's -T. From the man page, it doesn't really look like
there's an ssh_config option for -N.
-----Original Message-----
From: openssh-unix-dev [mailto:openssh-unix-dev-bounces+scott_n=xypro.com at
mindrot.org] On Behalf Of Scott Neugroschl
Sent: Tuesday, August 09, 2016 1:04 PM
To: Volker Diels-Grabsch; openssh-unix-dev at mindrot.org
Subject: RE: Equivalent ssh_config setting for "ssh -N"
RequestTTY no
-----Original Message-----
From: openssh-unix-dev [mailto:openssh-unix-dev-bounces+scott_n=xypro.com at
mindrot.org] On Behalf Of Volker Diels-Grabsch
Sent: Tuesday, August 09, 2016 9:19 AM
To: openssh-unix-dev at mindrot.org
Subject: Equivalent ssh_config setting for "ssh -N"
Dear OpenSSH developers,
Is there an equivalent ssh_config setting for the command line option
ssh -N ...
?
I want to connect to a server that doesn't provide an interactive shell but
allows for port forwarding only. I'd love to configure this into my
~/.ssh/config as follows:
Host foo
Hostname ...
Port ...
User ...
LocalForward ...
LocalForward ...
LocalForward ...
SomeSettingEquivalentToDashN yes
so I can call it via "ssh foo" instead of "ssh -N foo".
Are there good reasons not to provide such a setting?
Or, would you accept a patch that introduces such a setting?
If so, how sould this setting be named?
Regards,
Volker
--
Volker Diels-Grabsch
----<<<((()))>>>----
_______________________________________________
openssh-unix-dev mailing list
openssh-unix-dev at mindrot.org
https://lists.mindrot.org/mailman/listinfo/openssh-unix-dev
_______________________________________________
openssh-unix-dev mailing list
openssh-unix-dev at mindrot.org
https://lists.mindrot.org/mailman/listinfo/openssh-unix-dev
Hi all,
Thanks for the quick responses. So it seems there is really no
ssh_config option for -N.
So how should such an option be named? I propose:
default == ExecRemoteCommand yes
-N == ExecRemoteCommand no
Does that make sense?
Regards,
Volker
Scott Neugroschl schrieb:> Oops. That's -T. From the man page, it doesn't really look like
there's an ssh_config option for -N.
>
>
> -----Original Message-----
> From: openssh-unix-dev [mailto:openssh-unix-dev-bounces+scott_n=xypro.com
at mindrot.org] On Behalf Of Scott Neugroschl
> Sent: Tuesday, August 09, 2016 1:04 PM
> To: Volker Diels-Grabsch; openssh-unix-dev at mindrot.org
> Subject: RE: Equivalent ssh_config setting for "ssh -N"
>
> RequestTTY no
>
> -----Original Message-----
> From: openssh-unix-dev [mailto:openssh-unix-dev-bounces+scott_n=xypro.com
at mindrot.org] On Behalf Of Volker Diels-Grabsch
> Sent: Tuesday, August 09, 2016 9:19 AM
> To: openssh-unix-dev at mindrot.org
> Subject: Equivalent ssh_config setting for "ssh -N"
>
> Dear OpenSSH developers,
>
> Is there an equivalent ssh_config setting for the command line option
>
> ssh -N ...
>
> ?
>
> I want to connect to a server that doesn't provide an interactive shell
but allows for port forwarding only. I'd love to configure this into my
~/.ssh/config as follows:
>
> Host foo
> Hostname ...
> Port ...
> User ...
> LocalForward ...
> LocalForward ...
> LocalForward ...
> SomeSettingEquivalentToDashN yes
>
> so I can call it via "ssh foo" instead of "ssh -N foo".
>
> Are there good reasons not to provide such a setting?
> Or, would you accept a patch that introduces such a setting?
> If so, how sould this setting be named?
>
>
> Regards,
> Volker
>
> --
> Volker Diels-Grabsch
> ----<<<((()))>>>----
> _______________________________________________
> openssh-unix-dev mailing list
> openssh-unix-dev at mindrot.org
> https://lists.mindrot.org/mailman/listinfo/openssh-unix-dev
> _______________________________________________
> openssh-unix-dev mailing list
> openssh-unix-dev at mindrot.org
> https://lists.mindrot.org/mailman/listinfo/openssh-unix-dev
> _______________________________________________
> openssh-unix-dev mailing list
> openssh-unix-dev at mindrot.org
> https://lists.mindrot.org/mailman/listinfo/openssh-unix-dev
--
Volker Diels-Grabsch
----<<<((()))>>>----
Sound good to me. I've also looked for this ssh_config option recentlyu so this would be a welcome addition. Anthony On 10 Aug 2016 at 10:19:11, Volker Diels-Grabsch wrote:> Hi all, > > Thanks for the quick responses. So it seems there is really no > ssh_config option for -N. > > So how should such an option be named? I propose: > > default == ExecRemoteCommand yes > -N == ExecRemoteCommand no > > Does that make sense? > > > Regards, > Volker > > > Scott Neugroschl schrieb: > > Oops. That's -T. From the man page, it doesn't really look like there's an ssh_config option for -N. > > > > > > -----Original Message----- > > From: openssh-unix-dev [mailto:openssh-unix-dev-bounces+scott_n=xypro.com at mindrot.org] On Behalf Of Scott Neugroschl > > Sent: Tuesday, August 09, 2016 1:04 PM > > To: Volker Diels-Grabsch; openssh-unix-dev at mindrot.org > > Subject: RE: Equivalent ssh_config setting for "ssh -N" > > > > RequestTTY no > > > > -----Original Message----- > > From: openssh-unix-dev [mailto:openssh-unix-dev-bounces+scott_n=xypro.com at mindrot.org] On Behalf Of Volker Diels-Grabsch > > Sent: Tuesday, August 09, 2016 9:19 AM > > To: openssh-unix-dev at mindrot.org > > Subject: Equivalent ssh_config setting for "ssh -N" > > > > Dear OpenSSH developers, > > > > Is there an equivalent ssh_config setting for the command line option > > > > ssh -N ... > > > > ? > > > > I want to connect to a server that doesn't provide an interactive shell but allows for port forwarding only. I'd love to configure this into my ~/.ssh/config as follows: > > > > Host foo > > Hostname ... > > Port ... > > User ... > > LocalForward ... > > LocalForward ... > > LocalForward ... > > SomeSettingEquivalentToDashN yes > > > > so I can call it via "ssh foo" instead of "ssh -N foo". > > > > Are there good reasons not to provide such a setting? > > Or, would you accept a patch that introduces such a setting? > > If so, how sould this setting be named? > > > > > > Regards, > > Volker > > > > -- > > Volker Diels-Grabsch > > ----<<<((()))>>>---- > > _______________________________________________ > > openssh-unix-dev mailing list > > openssh-unix-dev at mindrot.org > > https://lists.mindrot.org/mailman/listinfo/openssh-unix-dev > > _______________________________________________ > > openssh-unix-dev mailing list > > openssh-unix-dev at mindrot.org > > https://lists.mindrot.org/mailman/listinfo/openssh-unix-dev > > _______________________________________________ > > openssh-unix-dev mailing list > > openssh-unix-dev at mindrot.org > > https://lists.mindrot.org/mailman/listinfo/openssh-unix-dev > > -- > Volker Diels-Grabsch > ----<<<((()))>>>---- > _______________________________________________ > openssh-unix-dev mailing list > openssh-unix-dev at mindrot.org > https://lists.mindrot.org/mailman/listinfo/openssh-unix-dev-- Anthony R Fletcher Room 2033, Building 12A, http://dcb.cit.nih.gov/~arif National Institutes of Health, arif at mail.nih.gov 12A South Drive, Bethesda, Phone: (+1) 301 402 1741. MD 20892-5624, USA.
Dear OpenSSH developers, Volker Diels-Grabsch schrieb:> So how should such an option be named? I propose: > > default == ExecRemoteCommand yes > -N == ExecRemoteCommand no > > Does that make sense?I just went ahead and created a patch for OpenSSH. It would be great if somebody could review this. I took extra care to meet your high quality standards. BTW, I wonder whether the folloing save-flags can be removed: - "oexec_remote_command" (formerly "ono_shell_flag") - "orequest_tty" To my understanding, keeping "otty_flag" should be sufficient. Regards, Volker -- Volker Diels-Grabsch ----<<<((()))>>>---- -------------- next part -------------- A non-text attachment was scrubbed... Name: openssh-7.3p1_exec_remote_command_v1.patch Type: text/x-diff Size: 8148 bytes Desc: not available URL: <http://lists.mindrot.org/pipermail/openssh-unix-dev/attachments/20160810/fb9be51a/attachment-0001.bin>