Note on OpenSSH 8.x port

[Randall]

Hi All,

We have found some issues with the OpenSSH 8.x port. Communications do not appear to be working correctly at present. While we are investigating, this may take a significant amount of time as we are a volunteer organization. As a result, finding and fixing issues does not come ahead of our day jobs.

OpenSSH 8.x has significant value in terms of key management and content signing capabilities. We still suggest using it for that purpose. However, NonStop SSH should be used for communications between systems.

Thank you for your patience,

Randall Becker
On behalf of the ITUGLIB Technical Committee

[Randall]

Post by Randall
Hi All,
We have found some issues with the OpenSSH 8.x port. Communications do not appear to be working correctly at present. While we are investigating, this may take a significant amount of time as we are a volunteer organization. As a result, finding and fixing issues does not come ahead of our day jobs.
OpenSSH 8.x has significant value in terms of key management and content signing capabilities. We still suggest using it for that purpose. However, NonStop SSH should be used for communications between systems.
Thank you for your patience,
Randall Becker
On behalf of the ITUGLIB Technical Committee

The root cause of this issue is incompatibilities between /usr/local/bin/ssh (the standard location) and _RLD_LIB_PATH. If your location for the appropriate OpenSSL version is not in your environment, you will get

Read from remote host github.com: Invalid function argument

This happens when your ssh location is not standard and OpenSSH tries to run /usr/local/bin/ssh that may use a different OpenSSL version from the one you are running. The fix is to ensure that /usr/local/bin/ssh is the proper ssh you intend to run and that _RLD_LIB_PATH is set correctly.