[Contents] [Index]

About This Document >>     Installing SSH Tectia Server for IBM z/OS >>     Getting Started with SSH Tectia Server for IBM z/OS >>     Configuring the Server >>     Configuring the Client >>     Authentication >>     File Transfer Using SFTP >>     File Transfer Using Transparent FTP Tunneling >>     Tunneling on the Command Line >>     Troubleshooting SSH Tectia Server for IBM z/OS >>     Advanced Information >>     Man Pages >>         scp2         sftp2         ssh-add2         ssh-agent2         ssh-socks-proxy >>         ssh-socks-proxy-config             Document Type Declaration and the Root Element             The general Element             The default-settings Element             The profiles Element             The static-tunnels Element             The filter-engine Element             The logging Element         ssh-socks-proxy-ctl >>         ssh-certd         ssh_certd_config         ssh-certview >>         ssh-cmpclient >>         ssh-dummy-shell         ssh-ekview         ssh-externalkeys         ssh-keydist2 >>         ssh-keygen2         ssh-probe2         ssh-scepclient >>         ssh-sft-stage         ssh2         ssh2_config         sshd-check-conf         sshd2         sshd2_config         sshd2_subconfig         sshregex     Log Messages >>

ssh-socks-proxy-config

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):

1. 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.

2. 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.

3. 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.

The default configuration file locations are:

• default configuration: /etc/ssh2/ssh-tectia/auxdata/ssh-broker-ng/ssh-socks-proxy-config-default.xml
• global configuration: /etc/ssh2/ssh-socks-proxy-config.xml
• user-specific configuration: $HOME/.ssh2/ssh-socks-proxy-config.xml

The XML DTD can be found in the /etc/ssh2/ssh-tectia/auxdata/ssh-broker-ng directory.

Document Type Declaration and the Root Element

The general Element

The default-settings Element

The profiles Element

The static-tunnels Element

The filter-engine Element

The logging Element

[Contents] [Index]