The SOCKS Proxy configuration file ssh-socks-proxy-config.xml is a valid XML file.
The SOCKS Proxy reads three configuration files (if all are available):
The ssh-socks-proxy-config-default.xml file is read first. It holds the factory default settings. It is not recommended to edit the file, but you can use it to check the default settings.
This file must be available and correctly formatted for the SOCKS Proxy to start.
Next, the SOCKS Proxy reads the global configuration file. The settings in the global configuration file override the default settings.
If the global configuration file is missing or malformed, the SOCKS Proxy will start normally. A malformed global configuration file is ignored and no settings in it are used.
Last, the SOCKS Proxy reads the user-specific configuration file if it is available. The settings in the user-specific configuration file override the settings in the global configuration file, with the following exceptions:
The settings under the key-stores, profiles, and static-tunnels elements from the user-specific configuration are combined with the settings of the global configuration file. If a connection profile with the same name has been defined in both the global configuration file and user-specific configuration file, the latter is used.
If the strict-host-key-checking and accept-unknown-host-keys elements have different values in the global and user-specific configuration, the more secure of these values is used.
If the user-specific configuration file is missing, the SOCKS Proxy will start using the previously read configuration files. However, if the user-specific configuration is malformed, the SOCKS Proxy will not start.