The SOCKS Proxy component consists of two processes:
The Tectia SOCKS Proxy process that needs to be running before transparent tunneling connections can be made. The Tectia SOCKS Proxy started task can be controlled with the Tectia SSH Assistant ISPF application and with console modify commands. The process can also be started under USS or by using a JCL script.
For more information on the command-line options of ssh-socks-proxy, see the description of ssh-broker-g3 in Tectia Server 6.6 for IBM z/OS User Manual Appendix Command-Line Tools and Man Pages. (Running ssh-socks-proxy will actually run ssh-broker-g3 in the SOCKS Proxy mode, using the
ssh-socks-proxy-config.xmlconfiguration files and with connection caching disabled.)
Control process for the SOCKS Proxy. It can be used, for example, to view the status of the SOCKS Proxy, to reconfigure or stop the SOCKS Proxy, or to load private keys to memory.
For more information on the ssh-socks-proxy-ctl options and commands, see the description of ssh-broker-ctl in Tectia Server 6.6 for IBM z/OS User Manual Appendix Command-Line Tools and Man Pages.
In the Tectia SSH Assistant ISPF application you can control the SOCKS Proxy (ssh-socks-proxy) via submenu 4.3 TSXP.
Table 8.1 contains a summary of the modify commands and Tectia SSH Assistant options for controlling the SOCKS Proxy. They are described in more detail in the following sections.
Table 8.1. Controlling the SOCKS Proxy server
|Set trace level|
|Set options for starting|
|Get status information|
|Get cryptographic algorithms information|
|List open channels|
|List open connections|
|Get the status of a connection|
|Close a connection|
The console messages generated by the SOCKS Proxy are listed in Table E.2.