This is a discussion on "Include" directive in ~/.ssh/config within the OpenSSH Development forums, part of the Networking and Network Related category; -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I would like an 'Include' directive or similar for ssh client config files. My ~/....
|
|||||||
| FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
|
|||
|
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1 I would like an 'Include' directive or similar for ssh client config files. My ~/.ssh/config file is larger than I would like, 147 Host stanzas currently (and I doubt I set any record there). I have some networks/hosts I access via some pretty complex setups (port-fwded SSH via intermediate hosts, multiple port-fwds for various applications, or just hosts where my username isn't the default or I use an alternate Identity file, etc). And several others, coworkers etc have similar, overlapping needs. I would like to group these logically into 'labname.conf', 'clientname.conf', 'localnet.conf', etc files, and my ~/.ssh/config file could be consolidated with a few: Include localoverrides.conf Include labname.conf Include clientname.conf Include localnet.conf ....or whatever. Then we can share / track via CVS or whatever these ..conf files, and not have to muck around with maintaining large, clutter-prone ~/.ssh/config files. An obvious alternative is to build a consolidated ~/.ssh/config file from these individual bits using a perl script, Makefile, etc. Has anybody else got similar needs, and if so have you already solved them with either a patch to openssh, or the script approach? Thanks, Hank Leininger <hlein@progressive-comp.com> D639 2E70 96A4 96D4 9AB6 95D6 A8FD BA7C 7093 F8F3 -----BEGIN PGP SIGNATURE----- iD8DBQFGeWOyqP26fHCT+PMRAiKeAJ9x17KSabcEX/4cVJOqWHaKwy6REwCcDl+E 1mr7QpKwVdTXYDfkg3eQzoo= =j0ie -----END PGP SIGNATURE----- _______________________________________________ openssh-unix-dev mailing list openssh-unix-dev@mindrot.org http://lists.mindrot.org/mailman/lis...enssh-unix-dev |