Comments on: (Semi-)Automated ~/.ssh/config management https://backreference.org/2015/03/08/semi-automated-sshconfig-management/ Proudly uncool and out of fashion Sun, 01 Oct 2017 21:39:46 +0000 hourly 1 https://wordpress.org/?v=5.8.2 By: waldner https://backreference.org/2015/03/08/semi-automated-sshconfig-management/#comment-25314 Sun, 01 Oct 2017 21:39:46 +0000 http://backreference.org/?p=5225#comment-25314 In reply to Lomanic.

Thanks for the pointers, I'll have a look. Mine was a crude hack indeed, and aimed to solve just a very specific use case I had at the time.

]]> By: Lomanic https://backreference.org/2015/03/08/semi-automated-sshconfig-management/#comment-25313 Thu, 28 Sep 2017 10:55:35 +0000 http://backreference.org/?p=5225#comment-25313 Hi, interesting article (and blog) here, you might be interested in https://github.com/kevinburke/ssh_config, a very complete ssh_config parser/writer for the Go programming language. I think the Perl equivalent would be http://search.cpan.org/dist/Net-SSH-Perl/lib/Net/SSH/Perl/Config.pm.

I can't speak for the Perl lib, but the Go one aims to save existing comments/does not overwrite the file as your script does.

]]> By: waldner https://backreference.org/2015/03/08/semi-automated-sshconfig-management/#comment-25284 Wed, 10 May 2017 13:12:39 +0000 http://backreference.org/?p=5225#comment-25284 In reply to ticolensic.

Sure, but the Include option appeared in OpenSSH 7.3, released more than one year after the article was written. It's good to point out that currently such possibility exists, though. Thanks.

]]> By: ticolensic https://backreference.org/2015/03/08/semi-automated-sshconfig-management/#comment-25283 Wed, 10 May 2017 13:00:12 +0000 http://backreference.org/?p=5225#comment-25283 Sorry to interrupt, but:

man ssh_config
--------------
Include
Include the specified configuration file(s). Multiple pathnames may be specified and each pathname may contain glob(3) wildcards and, for user configura‐
tions, shell-like ‘~’ references to user home directories. Files without absolute paths are assumed to be in ~/.ssh if included in a user configuration file
or /etc/ssh if included from the system configuration file. Include directive may appear inside a Match or Host block to perform conditional inclusion.

I guess you don't need no #comment sections

]]>