Your browser does not support HTML5 local storage or you have disabled it. Some functionality on this site, including saving your privacy settings and offering you special discounts, uses local storage and may not work with local storage disabled. We recommend allowing the use of local storage in your browser. In some browsers, it is the same setting used for disabling cookies.
The SOCKS Proxy will search and use keys from the following locations:
keys defined in the key-store element in the /opt/tectia/etc/ssh-socks-proxy-config.xml file
keys defined in the key-store element in the $HOME/.ssh2/ssh-socks-proxy-config.xml file
keys defined in the $HOME/.ssh2/identification file
keys found in the $HOME/.ssh2 directory
To get the SSHSP user's key information, you need to run ssh-socks-proxy-ctl as a UID 0 user on the USS side and give the -a /tmp/ssh-<user who started ssh-socks-proxy>/ssh-socks-proxy option to it.
To list the public-key pairs that are available for the SOCKS Proxy, give the following command:
# /opt/tectia/bin/ssh-socks-proxy-ctl list-keys -a /tmp/ssh-SSHSP/ssh-socks-proxy
The command prints a list of available private keys, showing basic key attributes such as key type, size and possible file name or key provider information. Also fingerprint and key identifier are displayed. The key identifier is a number that is used by other ssh-socks-proxy-ctl commands to identify the private key uniquely.
Running the command with the -s option produces a shorter output, for example (key hash value omitted):