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

SSH

Reconfiguring ssh-broker-g3

If you make changes to the ssh-broker-config.xml configuration file the changes will not take effect until the Connection Broker is reconfigured. After you have reconfigured the Connection Broker, existing connections will continue to use the old configuration settings while new connections will use the reconfigured settings.

You can reconfigure the Connection Broker to the current configuration file by executing one of the following commands.

  • Under USS:

    $ /opt/tectia/bin/ssh-broker-g3 --reconfig
    

    OR

    $ /opt/tectia/etc/init.d/ssh-broker-g3 reconfig
    

    OR

    $ /opt/tectia/bin/ssh-broker-ctl reload
    

    For example, when a user SSHBRKR owns the ssh-broker-g3 process:

    # /opt/tectia/bin/ssh-broker-ctl -a /tmp/ssh-SSHBRKR/ssh-broker reload
    
  • Under MVS, when you are running the Connection Broker as a started task:

    == > s sshbrkr,f=reconfig
    


 

 
Highlights from the SSH.COM blog:

  • Cryptomining with the SSH protocol: what big enterprises need to know about it

    Cryptomining malware is primarily thought of as targeting desktops and laptops and is used to hijack system resources to mine cryptocurrency.
    Read more
  • SLAM the door shut on traditional privileged access management

    Did you know that something as trivial-sounding as granting access for your developers or third parties to a product development environment can throw a gorilla-sized monkey wrench into your operations and productivity?
    Read more
  • We broke the IT security perimeter

    Everyone understands the concept of a security perimeter. You only gain access if you are identified and authorized to do so.
    Read more