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

SSH

Server Authentication with Public Keys

Use the sample JCL HOSTSAVE (shown below) from <HLQ>.V663.SAMPLIB to accept host keys without user interaction. Edit the JCL to suit your needs. You can consult the Tectia Server for IBM z/OS User Manual for an explanation of all the available options for the ssh-keydist-g3 command.

HOSTSAVE:

//HOSTSAV EXEC PGM=BPXBATSL,REGION=0M,TIME=NOLIMIT
//STDPARM  DD  *
PGM /opt/tectia/bin/ssh-keydist-g3
  -v 1 -N 2 -F plain 3 -i 4 -A /tmp/newhosts.log 5
  host1 host2 host3 6
//STDENV   DD  DSN=<HLQ>.V663.PARMLIB(SSHENV),DISP=SHR 7
//STDOUT   DD  SYSOUT=*
//STDERR   DD  SYSOUT=*
//STDIN    DD  DUMMY
//*
1

Enable verbose mode.

2

Accept new host keys automatically.

3

Store the accepted host keys in plain file name format.

4

Store the accepted host keys also using the IP addresses of the hosts.

5

The accepted host keys will be listed in the log file specified here.

6

Your host names or IP addresses go here.

7

Required environment variables are set here (see Environment Variables).



Want to see how PrivX can help your organisation?

Are you a DEVELOPER accessing cloud hosts, are you a IT ADMIN managing access & credentials in your corporation, are you BUSINESS MANAGER and want to save money or are you responsible of IT SECURITY in DevOps