When running a remote proxy job, we see an error:
11/12/2020 19:35:01.153+0000 1 ProxyPlugin.38749.6698523_1/WAAE_WF0.1/MAIN[Proxy].ProxyConnection.connect[:354] - Exception: com.jscape.inet.ssh.SshException: com.jscape.util.l.a.d cause = com.jscape.util.l.a.d ;wobId = 38749.6698523_1/WAAE_WF0.1/MAIN ;retryCount = 1
11/12/2020 19:35:01.153+0000 1 ProxyPlugin.38749.6698523_1/WAAE_WF0.1/MAIN[Proxy].ProxyConnection.connect[:355] - com.jscape.inet.ssh.SshException: com.jscape.util.l.a.d
at com.jscape.inet.ssh.Ssh.wrap(Unknown Source)
at com.jscape.inet.ssh.Ssh.connect(Unknown Source)
at cybermation.plugins.proxy.tasks.SSH2Connection.connectAndLogon(SSH2Connection.java:214)
at cybermation.plugins.proxy.ProxyConnection.connect(ProxyConnection.java:323)
at cybermation.plugins.proxy.ProxyConnection.<init>(ProxyConnection.java:240)
at cybermation.plugins.proxy.RemoteExecutionHandler.run(RemoteExecutionHandler.java:217)
at java.lang.Thread.run(Thread.java:748)
Caused by: com.jscape.util.l.a.h: com.jscape.util.l.a.d
at com.jscape.inet.ssh.protocol.v2.connection.SessionConnector.connect(Unknown Source)
at com.jscape.inet.ssh.protocol.v2.connection.SessionConnector.connect(Unknown Source)
at com.jscape.inet.ssh.Ssh.openSessionConnection(Unknown Source)
at com.jscape.inet.ssh.Ssh.connect(Unknown Source)
at cybermation.plugins.proxy.tasks.SSH2Connection.connectAndLogon(SSH2Connection.java:214)
at cybermation.plugins.proxy.ProxyConnection.connect(ProxyConnection.java:323)
at cybermation.plugins.proxy.ProxyConnection.<init>(ProxyConnection.java:240)
at cybermation.plugins.proxy.RemoteExecutionHandler.run(RemoteExecutionHandler.java:217)
at java.lang.Thread.run(Thread.java:748)
Caused by: com.jscape.util.l.a.d: null
at com.jscape.util.l.a.fb.read(Unknown Source)
at com.jscape.inet.ssh.protocol.v2.transport.TransportConnection.a(Unknown Source)
Release : 11.4
Component : CA Workload Automation System Agent
Certain SSH client and server key exchange (Kex) algorithms, example: diffie-hellman-group14-sha1, are being blocked out on some level of network/operating system restrictions.
Force stronger KexAlgorithm in the sshd configuration.
1) Backup /etc/ssh/sshd_config
2) Look for a KexAlgorithms parameter
KexAlgorithms ecdh-sha2-nistp256,ecdh-sha2-nistp384,ecdh-sha2-nistp521,diffie-hellman-group14-sha1,diffie-hellman-group-exchange-sha256
Note: On some machines the above parameter maybe totally missing, which means, internal defaults are being used
3) Modify (or create a brand new parameter if it is not present at all) the KexAlgorithms entry like below
KexAlgorithms diffie-hellman-group-exchange-sha256
4) restart sshd
5) restart the agent
Agent code would be enhanced in future to allow some level of customization of these algorithms.