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

SSH Tectia

Running ssh-broker-g3 as a Started Task

If ssh-broker-g3 is going to be run as a started task, you need to assign a user for running it.

  1. Assign a user to the started task by defining the procedure in the STARTED class and entering the user ID in the STDATA segment, for example, for user SSHBRKR:

    RDEFINE STARTED SSHBRKR.* STDATA(USER(SSHBRKR)GROUP(SYS1))
    SETROPTS RACLIST(STARTED) REFRESH 
    
  2. Create the USS home directory /u/SSHBRKR for the user. Under it, create the .ssh2 subdirectory for storing the remote server host keys (and optionally user keys and the user-specific ssh-broker-config.xml configuration file). Make the user the owner of these directories, for example:

    # mkdir /u/SSHBRKR
    # mkdir /u/SSHBRKR/.ssh2
    # chown -R SSHBRKR /u/SSHBRKR
    # chmod 700 /u/SSHBRKR/.ssh2
    

To run the Connection Broker as a started task, you can use the JCL procedure SSHBRKR from SAMPLIB (shown below). The JCL must be installed in the procedure library.

[Note]Note

The directory /tmp/ssh-USER (for example, /tmp/ssh-SSHBRKR) should be owned by the USER and its permission bits should be set to 700. The files /tmp/ssh-USER/ssh-broker and /tmp/ssh-USER/ssh-broker-aa should be owned by the USER and their permission bits should be set to 600. These permissions are normally set automatically when ssh-broker-g3 is run for the first time and they should not be changed.

SSHBRKR:

//SSHBRKR PROC F=CONSOLE
//SSHFTP  EXEC PGM=BPXBATSL,
//             REGION=0M,
//             TIME=NOLIMIT,
//             PARM='PGM /opt/tectia/bin/ssh-broker-g3 --&F'
//STDENV   DD  DSN=&SYSUID..SSZ.SAMPLIB(SSHENV),
//             DISP=SHR
//STDOUT   DD  PATH='/u/&SYSUID/broker.stc.stdout',
//             PATHOPTS=(OWRONLY,OCREAT,OTRUNC),
//             PATHMODE=(SIRUSR,SIWUSR)
//STDERR   DD  PATH='/u/&SYSUID/broker.stc.stderr',
//             PATHOPTS=(OWRONLY,OCREAT,OTRUNC),
//             PATHMODE=(SIRUSR,SIWUSR)
//STDIN    DD  DUMMY
//        PEND

Start the Connection Broker with the following operator command:

== > s sshbrkr 


 

 
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