atlassian / atlassian/jsm-integration-scripts

SSH Handshake Error

Open
#95 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
Python
Stars
17
Forks
10
PR merge metrics
No merged PRs in 30d

Description

I'm not sure if the JEC is still being developed or if its been abandoned, but I'm getting a handshake error when trying to connect to a git repo.

At first, it told me that it couldn't find the known_hosts file:
```
Could not read configuration: unable to find any valid known_hosts file, set SSH_KNOWN_HOSTS env variable
```
The `SSH_KNOWN_HOSTS` environment variable isn't documented on https://support.atlassian.com/jira-service-management-cloud/docs/configure-jira-edge-connector/ but I added the path in my config.

Then it fails to connect with a handshake error.
```
Could not read configuration: ssh: handshake failed: ssh: no common algorithm for key exchange; client offered: [curve25519-sha256@libssh.org ecdh-sha2-nistp256 ecdh-sha2-nistp384 ecdh-sha2-nistp521 diffie-hellman-group14-sha1], server offered: [diffie-hellman-group14-sha256 diffie-hellman-group16-sha512 diffie-hellman-group-exchange-sha256 diffie-hellman-group18-sha512 kex-strict-s-v00@openssh.com]
```

Is there another hidden SSH environment variable that resolves this, or is JEC using an outdated SSH implementation? I asked ChatGPT and it said that JEC is using github.com/go-git/go-git/v5 v5.2.0 and it does have a key exchange property that could be set, but I'm not seeing any configuration or environment variable documented to handle that.

Contributor guide

Open the contributing guide

Research direction

Start by reviewing the JEC SSH configuration and its use of go-git/v5, including the documented SSH_KNOWN_HOSTS setting and the reported key-exchange algorithms. Confirm whether the handshake can connect to the affected Git server with supported configuration, and document or fix the required setting so the connection succeeds.

Written by the indexing model from the issue text.

Assessment

Tech stack
git, go
Domain
networking
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.