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

SSH Tectia 
PreviousNextUp[Contents] [Index]

    About This Document >>
    Installing SSH Tectia Server for IBM z/OS >>
    Getting Started with SSH Tectia Server for IBM z/OS >>
    Configuring the Server >>
    Authentication >>
    System Administration >>
    File Transfer Using SFTP >>
    Secure File Transfer Using Transparent FTP Security >>
        Introduction to Transparent FTP Security
        Configuring SOCKS Proxy >>
        Creating the SSHSP User
        Running SOCKS Proxy >>
        Configuring FTP >>
        Examples of Transparent FTP Security>>
    Tunneling >>
    Troubleshooting SSH Tectia Server for IBM z/OS >>
    Man Pages and Default Configuration Files >>
    Log Messages >>

Creating the SSHSP User

If ssh-socks-proxy is going to be run as a started task, you need to create a user for running it.

To create a user, for example SSHSP, to run the SSH Tectia SOCKS Proxy task, do the following steps:

  1. Create a user, for example using RACF:

    ADDUSER SSHSP NAME('SSH Tectia SOCKS Proxy') OWNER(IBMUSER) + 
    NOPASSWORD NOOIDCARD + 
    OMVS(HOME('/u/SSHSP') PROGRAM( /bin/false ) UID(50042))
    

  2. Assign the user SSHSP to the started task by defining the procedure in the STARTED class and entering the user ID in the STDATA segment, for example:
    RDEFINE STARTED SSHSP.* STDATA(USER(SSHSP)GROUP(SYS1))       
    SETROPTS RACLIST(STARTED) REFRESH  
    
  3. Create the USS home directory /u/SSHSP for the SSHSP user. Under it, create the .ssh2 subdirectory for storing the remote server host keys (and optionally user keys and the user-specific ssh-socks-proxy-config.xml configuration file). Make SSHSP the owner of these directories:
    # mkdir /u/SSHSP
    # mkdir /u/SSHSP/.ssh2
    # chown -R SSHSP /u/SSHSP
    # chmod 700 /u/SSHSP/.ssh2
    

PreviousNextUp[Contents] [Index]


[ Contact Information | Support | Feedback | SSH Home Page | SSH Products ]

Copyright © 2011 SSH Communications Security Corp.
This software is protected by international copyright laws. All rights reserved.
Copyright Notice


 

 
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