[RFC/PATCH v2] ssh: config directive to modify the local environment

[Daniel Kahn Gillmor]

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

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

That way, it would be possible for options like TCPKeepAlive to be
respected by compliant ProxyCommands.

This would require standardizing on a form -- maybe all-downcased,
prefixed with openssh_ ?

So the client process would get an environment that says:

 openssh_tcpkeepalive=yes
 openssh_user=foo
 openssh_addressfamily=inet6
  ...
 openssh_hostname=bar.example

This would let people make significantly better proxycommands and
localcommands, i think.

	--dkg

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 900 bytes
Desc: OpenPGP digital signature
URL: <http://lists.mindrot.org/pipermail/openssh-unix-dev/attachments/20110107/54884d70/attachment.bin>