On Mon, Jun 11, 2012 at 1:28 PM, jill <lists@bespokess.com> wrote:

> In lieu of being able to do ssh includes, a few people with the same
> idea seem to be doing things with ssh proxies that contain the more
> advanced configs, or running scripts in their bash profile that cat a
> bunch of disparate files together into one .ssh/config.  We could make
> the company-wide config a part of the global ssh conf for every system
> we use it on, until we get to stuff like my jumphost at home that I
> share with my family and need that data to be account/profile specific.

Well, you could conceivably apply options (I assume these are things
like keys, port forwards, etc) to the command line and create a
globally sourceable bashrc with aliases. EG:

cat > foowidget-ssh_config
alias ssh-foowidget='ssh -i ~/.ssh/foowidget.id_dsa'
^d

Then simply call it in a bashrc for each user. It ain't pretty by any
means, but it's moderately functional, and with proper group perms you
could conceivably walk through all of them on login and source them
all.

Alternately, 'cat /etc/global_ssh/config_foo_* ~/.ssh/config >
~/.ssh/config.global; alias ssh="ssh -F ~/.ssh/config.global"' in
everyones bashrc would work too.

~Ben
---------------------------------------------------
PLUG-discuss mailing list - PLUG-discuss@lists.plug.phoenix.az.us
To subscribe, unsubscribe, or to change your mail settings:
http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss