On Sun, 2023-01-08 at 11:50 +0100, Stefan Seyfried wrote:
debug1: Reading configuration data /home/seife/.ssh/config debug1: Reading configuration data /usr/etc/ssh/ssh_config debug1: /usr/etc/ssh/ssh_config line 24: include /etc/ssh/ssh_config.d/*.conf matched no files debug1: /usr/etc/ssh/ssh_config line 25: include /usr/etc/ssh/ssh_config.d/*.conf matched no files
Here we can see that the user config file is read first, and that it's no problem if no .conf files exist in these locations.
One example that it is actually using my ~/.ssh/config is, that it is sending COLORFGBG wich is configured there.
I would not bet that the order of including the files is "correct" (or as I would expect it to be), because I have no idea how openssh handles the order of setting and overriding options, but as /etc/ssh/ssh_config.d/ is empty here, this does not matter right now.
Exactly. (Side note: ssh configuration can be surprising sometimes, because in contrast to many other packages, the "the first obtained value for each parameter is used", with the notable exception of directives that can take multiple values, like IdentityFile or SendEnv). @Michael Ströder, it's still unclear to me how this change would have broken your setup. Regards, Martin