Hello @fds242,

This happens because of the order the configuration options are set. The priority order of the settings in libssh are:

1. Local user configurations (defaults to ~/.ssh/config)
2. System-wide configurations (defaults to /etc/ssh/ssh_config)
3. Application defaults (set through ssh_options_set(), if any)

The idea behind overriding the applications defaults with the global configurations is to keep the list of used algorithms up-to-date even when the application code is not frequently updated. And for the local configurations overriding the system-wide configurations is to give the user the option to easily override the system-wide defaults.

The problem here is that there are options set through curl_easy_setopt() which are expected to override even the local user configurations. The way to make it to behave as expected is to:

1. Set libcurl defaults through ssh_options_set()
2. Manually call ssh_options_parse_config() to parse the configuration files
   • The automatic configuration parsing will not happen if this is called. Therefore, it would be necessary to manually call the parsing for all configuration files to be considered
   • Options set in a configuration file cannot be overridden by options set in a configuration file parsed later, IOW, the first value seen is kept. As a result, the local configuration files should be parsed before the system-wide configuration files
3. Override anything set before by calling ssh_options_set() after the configuration parsing
   • This is where options passed through curl_easy_setopt() should be set

That proposed new ordering sounds perfect. Would be great if it worked like that with libcurl, keeping the OpenSSH config files as a source of defaults, but still allowing the developer – and in turn, the users of that developer's software – to have the last say over settings. What's a little curious is that it already behaves like this with certain options, such as taking a User username setting from ~/.ssh/config as the default, but still allowing a username specified by the libcurl user to override that.

Only minor observation I have is that it feels unfortunate if simply calling ssh_options_parse_config with NULL for a file name is not sufficient to fully recreate all the default OpenSSH config loading logic libssh does or might do in the future, reading both the system-wide and the user config files. For example, /etc/ssh/ssh_config might be a reasonable choice on a Unix-like system, but it's probably more akin to %programdata%\ssh\ssh_config on Windows. Likewise, just determining the user's home folder can vary by OS. If libssh normally already handles all those differences, or might in the future, it would be a shame to keep duplicating that in any libssh client program that need to be able to override options.

That proposed new ordering sounds perfect. Would be great if it worked like that with libcurl, keeping the OpenSSH config files as a source of defaults, but still allowing the developer – and in turn, the users of that developer's software – to have the last say over settings. What's a little curious is that it already behaves like this with certain options, such as taking a User username setting from ~/.ssh/config as the default, but still allowing a username specified by the libcurl user to override that.

Only minor observation I have is that it feels unfortunate if simply calling ssh_options_parse_config with NULL for a file name is not sufficient to fully recreate all the default OpenSSH config loading logic libssh does or might do in the future, reading both the system-wide and the user config files.

Actually libssh does exactly this: if NULL is provided as the file name, it parses the user configuration file followed by the global configuration file. The libssh documentation lacks this information and I'm sorry about this.

For example, /etc/ssh/ssh_config might be a reasonable choice on a Unix-like system, but it's probably more akin to %programdata%\ssh\ssh_config on Windows. Likewise, just determining the user's home folder can vary by OS. If libssh normally already handles all those differences, or might in the future, it would be a shame to keep duplicating that in any libssh client program that need to be able to override options.

The option to override the global default configuration file is provided as a libssh build configuration option. You can define GLOBAL_CLIENT_CONFIG when configuring the build to provide the system-wide default configuration file path for the client and GLOBAL_BIND_CONFIG for the server. It would look like this:

$ cmake -DGLOBAL_CLIENT_CONFIG=/path/to/client/config -DGLOBAL_BIND_CONFIG=/path/to/server/config /path/to/libssh/repo/clone

These configuration options were provided exactly to allow the responsible for building libssh (normally a package maintainer) to set the defaults for the target system.

I forgot to mention that you will need libssh >= 0.9.0 to have such behaviour. I understand it is quite new to be adopted as the minimum requirement as it was released last year. Maybe a solution would be to parse manually the configuration files for older versions, but I'm afraid there is no way to get the right system defaults for the global configuration files.

Hello @fds242, could you please check if the PR #5283 fixes the issue?

Thank you @ansasaki, tested & can confirm it does work as expected now! By no means an exhaustive test concerning all the options that could be affected. My original issue, overriding the known hosts file, does work now in that the curl option now gets the final say over an OpenSSH config file.