-
Bug
-
Resolution: Fixed
-
Critical
-
Windows Server 2012 x64
jre1.8.0_241
After upgrading to Trilead API v1.0.11 my connection to SSH clients fail with the error below:
[09/27/20 10:23:16] [SSH] WARNING: SSH Host Keys are not being verified. Man-in-the-middle attacks may be possible against this connection.
Key exchange was not finished, connection is closed.
SSH Connection failed with IOException: "Key exchange was not finished, connection is closed.", retrying in 5 seconds. There are 1 more retries left.
[09/27/20 10:23:22] [SSH] WARNING: SSH Host Keys are not being verified. Man-in-the-middle attacks may be possible against this connection.
Key exchange was not finished, connection is closed.
ERROR: Connection is not established!
I have reproduced this on two environments and get exactly the same results, downgrading to v1.0.10 fixes the issue.
- duplicates
-
JENKINS-63794 SSH agent - Key exchange was not finished, connection is closed
-
- Closed
-
- is duplicated by
-
JENKINS-63829 Git SSH connection fails in TriLead KexManager
-
- Closed
-
[JENKINS-63790] Trilead API v1.0.11 causes SSH agent connections to fail
Link |
New:
This issue duplicates |
Labels | New: regression |
Attachment | New: trilead-api.hpi [ 52759 ] |
Link |
New:
This issue is duplicated by |
Summary | Original: Trilead API v1.0.11 causes SSH slave connections to fail | New: Trilead API v1.0.11 causes SSH agent connections to fail |
Attachment | New: Screenshot 2020-10-12 at 18.36.42.png [ 52931 ] |
Attachment | New: Screenshot 2020-10-12 at 18.38.21.png [ 52932 ] |
Priority | Original: Major [ 3 ] | New: Critical [ 2 ] |
Comment | [ From where to get the trilead-api-1.0.12 and how to test it on existing Jenkins server? ] |
Resolution | New: Fixed [ 1 ] | |
Status | Original: Open [ 1 ] | New: Closed [ 6 ] |