This approach works well, and can scale. A critical part is to sanity check the result for compatibility. Nico Kadel-Garcia Email: nkadel@xxxxxxxxx Sent from iPhone > On Feb 18, 2015, at 17:11, shawn wilson <ag4ve.us@xxxxxxxxx> wrote: > >> On Feb 18, 2015 2:53 PM, "Hendrik Visage" <hvjunk@xxxxxxxxx> wrote: > >> >> Questions: >> - Is there anybody that see a value in a format/parser/matcher for >> ssh_config files to be able to merge/"diff"/sort these files? > > I've started on a perl module to go through an ssh config and compile what > ssh should do for a given host (mainly to only ssh-add a key when a host is > configured to use it). I would prefer an abstract config backend though. > >> - Any other ideas/solutions I could consider to manage these ssh_config > files? > > You can make a compile script that takes ordered parts of a config and > builds an ssh_config and then you're only checking in and/or comparing > project specific bits. > _______________________________________________ > openssh-unix-dev mailing list > openssh-unix-dev@xxxxxxxxxxx > https://lists.mindrot.org/mailman/listinfo/openssh-unix-dev _______________________________________________ openssh-unix-dev mailing list openssh-unix-dev@xxxxxxxxxxx https://lists.mindrot.org/mailman/listinfo/openssh-unix-dev
