[Doc] Extension of Included configuration files

[Jakub Jelen]

On 02/07/2017 10:55 PM, Alexis Horgix Chotard wrote:
> Hello,
>
> I'm really happy that the 7.3 release of OpenSSH introduced the
> Include directive.
>
> However, since there is absolutely no restriction or advice neither on
> the name nor on the location of the included files, it makes it harder
> for external tools to recognize them; I'm mainly thinking about text
> editors that would like to enable syntax coloration for it (
> https://github.com/vim/vim/pull/1452 ).
> Until now it wasn't a problem since the file was either `ssh_config`
> or `~/.ssh/config` in most cases - maybe all ? no idea if this is
> configurable.
>
> I would like to include a SHOULD part to the man section of the
> Include directive in an effort to make those included files
> recognizable.
> I'm sure you'll have a better suggestion for the wording than me;
> however you'll find a patch attached for the sentence "Configuration
> file(s) referenced by this Include directive should use the .sshconfig
> extension to be detected as such by external tools." but it could also
> be something simpler like "If you want external tools to detect your
> configuration files, they should use the .sshconfig extension".
>
> Let me know what you think about it,

This is very strict condition. For the tools, I would rather have a look 
at the full path (if it is possible), because in most of the cases, the 
files should come under /etc/ssh/ssh_config.d/*

Having this path automatically included by default in shipped 
configuration files from OpenSSH upstream would be nice.

Regards,
-- 
Jakub Jelen
Software Engineer
Security Technologies
Red Hat