[Bug 1585] Allow an `Include' option which reads another config file in place and does not error out when `Include' file not readable

[bugzilla-daemon at mindrot.org]

https://bugzilla.mindrot.org/show_bug.cgi?id=1585

--- Comment #21 from Tomas Pospisek <tpo_deb at sourcepole.ch> ---
@Jakub Jelen specifically, but to the other people here in general as
well.

I have not studied the proposed patches, but one problem that I am
seeing in general with the approach is, that once we start
including/merging multiple configurations, we will start seeing
conflicts of config options and overrides.

This does not *have to* be a big problem in specific cases, but it is a
problem in the general case, when one starts mixing configuration bits
coming from different sources with different trusts.

ssh does not warn when you have twice the same setting with different
options, so configuration snipplets from your company can override your
own settings without you noticing. It can change host settings. It can
change security settings. It can change how ssh connects to where.

I myself am using a "cat ~/.ssh/config.d/* > ~/.ssh/config" approach
myself and that certainly works and is useful for me, but I have also
been already bitten by the above mentioned problem once. It wasn't
anything serious, but stuff did start behaving slightly unexpectedly
until I noticed that an imported bit of ssh config had changed...

-- 
You are receiving this mail because:
You are watching the assignee of the bug.