Your browser does not allow storing cookies. We recommend enabling them.

SSH

Running Connection Broker

The Connection Broker component consists of two processes:

  • ssh-broker-g3: the Tectia Connection Broker process

  • ssh-broker-ctl: control process for the Connection Broker. It can be used, for example, to view the status of the Connection Broker, to reconfigure or stop the Connection Broker, or to load private keys to memory.

Normally, there is no need to start the ssh-broker-g3 process separately. The sshg3, scpg3, and sftpg3 client programs start it in the on-demand mode, and stop it when the client program is stopped.

If you are running several tunneling or file transfer jobs for a single user and do not want that a separate ssh-broker-g3 process starts each time one of these jobs is run, you can start ssh-broker- g3 in persistent mode. After that, all client programs run by the user will use the same instance of ssh-broker-g3. This saves system resources. The Connection Broker can be started under USS, or by using a JCL script or started task. The Connection Broker can also be started with the /opt/tectia/etc/init.d/ssh-broker-g3 script.


 

 
What to read next:

  • Reduce Secure Shell risk. Get to know the NIST 7966.



    The NISTIR 7966 guideline from the Computer Security Division of NIST is a direct call to action for organizations regardless of industry and is a mandate for the US Federal government.
    Download now
  • ISACA Practitioner Guide for SSH



    With contributions from practitioners, specialists and SSH.COM experts, the ISACA “SSH: Practitioner Considerations” guide is vital best practice from the compliance and audit community.
    Download now