SSH support

Wazi Developer for Eclipse supports Secure Shell (SSH) to offer secure, encrypted communications between your Windows workstation and z/OS® remote systems.

The SSH server on your remote system must be OpenSSH compliant and support the SSH2 protocol. The SSH server must also be configured to support the following methods of authentication:
  • Password authentication
  • Public key authentication

Only these authentication methods are supported. The default method is password authentication. When password authentication is enabled, you notice no difference in your interaction with the remote system. You are still prompted for a password the first time that you access the remote system in a session, however, the sign-on information is encrypted before it is sent to the remote system.

Key authentication is a more secure method of authentication. The first time that you access a remote system, a public key file is automatically generated and securely transferred to the remote system after you specify your password. Subsequent access to the remote system does not require a password; instead a key exchange occurs between the SSH Client and the remote server. If the keys match, the session is authenticated.

The SSH client for Wazi Developer for Eclipse is installed as an optional feature. If this feature is not installed, all preferences that relate to SSH are disabled and SSH communications cannot be used. When SSH protocol is enabled, you can use the SSH protocol to start the RSE server and to run all remote actions. All sign-on information and remote action inputs are encrypted. You can secure RSE transfers by using Secure Socket Layer (SSL) communications.
Note: File transfers are not encrypted since this type of encryption is controlled by RSE. NFS or SMB control encryption of file transfers if you are accessing a mounted file.