As400 Ssh

Posted : admin On 1/29/2022

The Secure Shell (SSH) was originally designed to provide mainly a secure remote login to and a file transfer utility between remote computers. The communication protocol is an SSH protocol that runs on top of Transmission Control Protocol (TCP). Currently, two protocols are supported, SSH1 and SSH2. 1 Bob Bittner ISV Strategy and Enablement Rochester, MN [email protected] +1.507.253.6664 OMNI 15-May-2007 Qshell and OpenSSH for IBM System i QShell In the beginning. Considering SSH is installed on your AS400 ie 5733SC1 (OpenSSH, OpenSSL, zlib) in LICPGM, you can start the SSH daemon.

Afternoon all,As400As400 SshAs400 Ssh

I'm trying to login into my V5R4 iSeries using Ubuntu SSH client,
works fine with user name and password but can not get it to work with
certificate. I've added the my client public key to the
authorized_key file and debug of login seems to show it being
recognised and accepted but it still requests password

As400 sftp command

Can anyone advise please, debug below

[email protected]:~$ ssh -v -n -o StrictHostKeyChecking=no
[email protected]

OpenSSH_5.1p1 Debian-5ubuntu1, OpenSSL 0.9.8g 19 Oct 2007
Pseudo-terminal will not be allocated because stdin is not a terminal.
debug1: Reading configuration data /etc/ssh/ssh_config
debug1: Applying options for *
debug1: Connecting to 10.1.1.1 [10.1.1.1] port 22.
debug1: Connection established.
debug1: identity file /home/ubuntu/.ssh/identity type -1
debug1: identity file /home/ubuntu/.ssh/id_rsa type 1
debug1: Checking blacklist file /usr/share/ssh/blacklist.RSA-2048
debug1: Checking blacklist file /etc/ssh/blacklist.RSA-2048
debug1: identity file /home/ubuntu/.ssh/id_dsa type -1
debug1: Remote protocol version 1.99, remote software version
OpenSSH_3.5p1
debug1: match: OpenSSH_3.5p1 pat OpenSSH_3.*
debug1: Enabling compatibility mode for protocol 2.0
debug1: Local version string SSH-2.0-OpenSSH_5.1p1 Debian-5ubuntu1
debug1: SSH2_MSG_KEXINIT sent
debug1: SSH2_MSG_KEXINIT received
debug1: kex: server->client aes128-cbc hmac-md5 none
debug1: kex: client->server aes128-cbc hmac-md5 none
debug1: SSH2_MSG_KEX_DH_GEX_REQUEST(1024<1024<8192) sent
debug1: expecting SSH2_MSG_KEX_DH_GEX_GROUP
debug1: SSH2_MSG_KEX_DH_GEX_INIT sent
debug1: expecting SSH2_MSG_KEX_DH_GEX_REPLY
debug1: Host '10.1.1.1' is known and matches the RSA host key.
debug1: Found key in /home/ubuntu/.ssh/known_hosts:1
debug1: ssh_rsa_verify: signature correct
debug1: SSH2_MSG_NEWKEYS sent
debug1: expecting SSH2_MSG_NEWKEYS
debug1: SSH2_MSG_NEWKEYS received
debug1: SSH2_MSG_SERVICE_REQUEST sent
debug1: SSH2_MSG_SERVICE_ACCEPT received
debug1: Authentications that can continue: publickey,password,keyboard-
interactive
debug1: Next authentication method: publickey
debug1: Offering public key: /home/ubuntu/.ssh/id_rsa
debug1: Authentications that can continue: publickey,password,keyboard-
interactive
debug1: Trying private key: /home/ubuntu/.ssh/identity
debug1: Trying private key: /home/ubuntu/.ssh/id_dsa
debug1: Next authentication method: keyboard-interactive
debug1: Authentications that can continue: publickey,password,keyboard-
interactive
debug1: Next authentication method: password
[email protected]'s password:

When I am developing java programs in a linux box, I would access these programs using a command line in a PUTTY session. On the other hand, when I develop java programs in the AS400, I would access these java programs either via QSH or QP2TERM. Maybe there’s a way for me to access the AS400 the same way I do a linux box.

Turns out that with a few simple steps, we can also use PUTTY to connect to the AS400!

First thing that you must do is to ensure the SSH daemon is running in the AS400. Run the following from the AS400 command line:

Check that the job is running using WRKACTJOB:

Sftp Ibm I

Now create an SSH profile in putty [YourAS400Id]@[YourAS400IPAddress] and use it to connect to you AS400. Enter your password after being prompted for it then type in the command “pwd”. It should default to your home directory in the IFS

As400 Ssh

Now you can use PUTTY to access your java programs in the AS400 the same way you do it on a linux box!