Skip to content
This repository has been archived by the owner on Jan 8, 2024. It is now read-only.

GitHub SSH auth failure: You're using an RSA key with SHA-1, which is no longer allowed #3809

Closed
ishitatsuyuki opened this issue Sep 6, 2022 · 4 comments
Labels
question Further information is requested

Comments

@ishitatsuyuki
Copy link

Describe the bug
When cloning a GitHub repo with SSH auth, RSA private key, Waypoint fails with the following error:

Git clone failed: unknown error: ERROR: You're using an RSA key with SHA-1, which is no longer allowed. Please use a newer client or a different key type.

Output:

It looks like this is an issue with a dependency: go-git/go-git#411

Steps to Reproduce

  1. Install Waypoint. My cluster is using Nomad.
  2. Create a deploy key on GitHub (or use your personal SSH key). The key should use RSA (and not ECDSA).
  3. Add a project from the web UI, fill in a repo and the SSH key then apply. My repo was private but a public repo should work too.

Expected behavior

git clone should succeed.

Waypoint Platform Versions

  • Waypoint CLI Version: v0.9.1
  • Waypoint Server Platform and Version: nomad v0.9.1
  • Waypoint Plugin: N/A
@ishitatsuyuki
Copy link
Author

ishitatsuyuki commented Sep 6, 2022

Using an ECDSA key can workaround this. Kinda obvious but fwiw.

@briancain
Copy link
Member

Hey there @ishitatsuyuki - This looks to be working as expected, and the error message seems descriptive enough to get you unblocked. SSH has also removed support for RSA SHA-1 keys, so at this time there isn't much that Waypoint can do for you with this issue. For now, I'm going to go ahead and close this but thank you for opening the issue!

@briancain briancain closed this as not planned Won't fix, can't repro, duplicate, stale Sep 7, 2022
@briancain briancain added question Further information is requested and removed new labels Sep 7, 2022
@ishitatsuyuki
Copy link
Author

TBH this looks like a fairly poor out of box experience, but if you have other stuff to prioritize I guess it's OK to skip this for now.

@ishitatsuyuki
Copy link
Author

@briancain It looks like this has been fixed upstream. It still hasn't got a tagged release, but please consider reopening this and update the dep once it gets tagged.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
question Further information is requested
Projects
None yet
Development

No branches or pull requests

2 participants