[RFC/PATCH v2] ssh: config directive to modify the local environment
Bert Wesarg
bert.wesarg at googlemail.com
Sat Jan 8 06:50:34 EST 2011
On Fri, Jan 7, 2011 at 17:42, Daniel Kahn Gillmor <dkg at fifthhorseman.net> wrote:
> On 01/07/2011 07:00 AM, Bert Wesarg wrote:
>> This provides a mechanism to attach arbitrary configure options into the
>> ssh_config file and use them from the LocalCommand and ProxyCommand.
>
> The user can already do this by just exporting a given environment
> before invoking ssh, right, or by embedding the environment variables in
> the LocalCommand or ProxyCommand itself:
>
> ssh -oProxyCommand='env FOO=bar BAZ=qux othercommand' foo at bar.example
Sure. But honestly I think that will become quiet cumbersome if you
have more than 2 variables, which depend on the connecting host.
>
> However, I'd be interested in seeing this kind of work done to export
> the ssh config itself to the child processes:
>
> https://bugzilla.mindrot.org/show_bug.cgi?id=1766
I know about this. I would suggest to extend the expand code to handle this.
>
> That way, it would be possible for options like TCPKeepAlive to be
> respected by compliant ProxyCommands.
That would be:
ProxyCommand command %{TCPKeepAlive}
This way we could handle the case internally. I also think that my
proposed LocalEnvMod would benefit from this.
I can provide a patch the next week. The old %<char> syntax ould be
deprecated over time.
Bert
>
> --dkg
>
>
More information about the openssh-unix-dev
mailing list