On Friday, August 9, 2019 at 1:12:55 PM UTC-4, Walter Cazzola wrote:
> On Fri, 9 Aug 2019, 'Grant Taylor' via vim_use wrote:
>
> >> Any idea?
>
> > Yes.
>
> > Teach OpenSSH how to get to the host by putting entries in the OpenSSH
> > /client/ configuration file; ~/.ssh/config or system wide
> > /etc/ssh/ssh_config. E.g.
>
> > Host targetHost
> > ProxyCommand ssh -W %h:%p tunnel-host
>
> > Host tunnel-host
> > # any options you might want here
>
> > This teaches any and all OpenSSH clients how to get to targetHost without
> > needing to specify additional command line options. I.e. you can run the
> > following command:
>
> > gvim scp://targetHost+path
>
> > (G)vim doesn't need to worry about /how/ scp connects. OpenSSH's scp command
> > deals with that transparently.
>
> Good suggestion but isn't this forcing any ssh connection to pass through the
> tunnel? I would prefer something less radical or that, at least, I can easily
> switch off without touching every time the ssh configuration.
>
> Walter
>
> --
The tunnel would only be used for that host, which you already have to get to by going through the intermediate host. It isn't going to force other hosts to go through the same intermediate host.
Regardless, "Host" is only an alias. Call it whatever you want and use it just for vi.
--
--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/72796b33-4c66-45ac-9a7a-b637e00ab4c1%40googlegroups.com.
No comments:
Post a Comment