Skip to content

fix(ssh): add support for modern SSH key algorithms#608

Merged
jdubois merged 6 commits intojhipster:mainfrom
alexlukic:fix-607-ssh-key-support
Sep 26, 2025
Merged

fix(ssh): add support for modern SSH key algorithms#608
jdubois merged 6 commits intojhipster:mainfrom
alexlukic:fix-607-ssh-key-support

Conversation

@alexlukic
Copy link
Contributor

  • Added support for ed25519 and rsa-sha2 SSH deploy keys

  • Verified locally that connections now work using the new SSH key algorithms supported by GitHub

  • Built Docker image and tested it on existing ECR

  • Verified by deploying to current ECS cluster, replacing old image with the freshly built one

Fix #607

  • Please make sure the below checklist is followed for Pull Requests.

  • Travis tests are green

  • Tests are added where necessary

  • Documentation is added/updated where necessary

  • Coding Rules & Commit Guidelines as per our CONTRIBUTING.md document are followed

- Added support for ed25519 and rsa-sha2 SSH deploy keys

- Verified locally that connections now work using the new SSH key algorithms supported by GitHub

- Built Docker image and tested it on existing ECR

- Verified by deploying to current ECS cluster, replacing old image with the freshly built one

Fix jhipster#607
@alexlukic
Copy link
Contributor Author

Fixes #607 – added support for ed25519 and rsa-sha2 keys. Tested locally and ready for review.

.dockerignore Outdated
@@ -1,2 +1,2 @@
target
#target
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should this be reverted?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hi,

About the Dockerfile and .dockerignore adjustments:

The change in .dockerignore was needed only so the newly created Dockerfile could successfully build the test Docker image. I used that image in my own ECS development cluster to verify the new JHipster Registry version.

If this extra Dockerfile is not required in your official build process, then both the .dockerignore change can be reverted and the Dockerfile itself can be removed, since you will anyway be building and publishing the official image to DockerHub.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Reverted .dockerignore and removed Dockerfile form commit. Like it was before...

@jdubois
Copy link
Member

jdubois commented Sep 24, 2025

@alexlukic is this PR ready to be merged on your side? If yes, I'll have another look

@alexlukic
Copy link
Contributor Author

alexlukic commented Sep 24, 2025

@jdubois Yes it is, I made all suggestions that mraible asked. It is completely ready for merge from my side.

@jdubois
Copy link
Member

jdubois commented Sep 26, 2025

LGTM @alexlukic , thank you!!

@jdubois jdubois merged commit 6d0e096 into jhipster:main Sep 26, 2025
2 checks passed
@jdubois
Copy link
Member

jdubois commented Sep 26, 2025

@mraible we'll need to do a new release of JHipster Registry, do you want me to do it independently from a JHipster release? Or do you want to release everything at once next time?

@alexlukic
Copy link
Contributor Author

alexlukic commented Sep 26, 2025

LGTM @alexlukic , thank you!!

I have submitted a $300 bug bounty expense on the JHipster OpenCollective:
https://opencollective.com/generator-jhipster/expenses/266920
This PR fixes #608 and was merged by @jdubois. Thanks!

Also, thanks a lot @jdubois and @mraible for the quick review, guidance, and support!
Really appreciate the warm welcome and will be happy to stay in touch.

@mraible
Copy link
Contributor

mraible commented Sep 26, 2025

@jdubois It's probably best to do a release as the next JHipster release might be awhile. Tagging @DanielFran for his opinion.

@DanielFran
Copy link
Member

@jdubois @mraible Better to do a release now for registry only

@jdubois
Copy link
Member

jdubois commented Sep 30, 2025

I see the GitHub Action is outdated and a release will be complicated -> I'm having a look, and I'll probably work directly on the main branch as I want to fix the GitHub Action, so don't be surprised

@jdubois
Copy link
Member

jdubois commented Oct 1, 2025

Release v7.5.0 done (I also upgraded several dependencies in the process), and I just opened a PR to the main project in order to include this version in the next release: jhipster/generator-jhipster#30934

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[Bug] JHipster Registry fails with GitHub SSH deploy keys (ed25519 / rsa-sha2) – works only with legacy RSA-SHA1

4 participants