Changes to the ssh_config file that might require a migration action

Table 1 lists the changes to the ssh_config file that might require a migration action and the accompanying actions.

Table 1. Changes to the ssh_config file that might require a migration action
What changed Migration action needed?

The ControlPath keyword

Previously, %l in the path was substituted by the local host name. Now, %l in the path is substituted by the local host name (including any domain name).

Yes, if you want to use substitute character to substitute the local host name without any domain name.

Action: Use the %L in the path to substitute the first component of the local host name.

The RemoteForward keyword

Previously, the port argument "0" was not supported. Now, if the port argument is “0”, the listen port will be dynamically allocated on the server and reported to the client at run time.

No, set the port argument to 0 was considered to be illegal in the previous version.

The RhostsAuthentication keyword

Previously, this option was supported for protocol version 1. Now this option is no longer supported for protocol version 1 on z/OS UNIX.

Yes, if you use RhostsAuthentication for protocol version 1 in your application. When setting this, you will receive the following message: filename line line_number: Deprecated option keyword.

Action: Update your application.