Skip to content

Conversation

@mufeedali
Copy link
Contributor

Fixes #1257

Summary

Adds support for using an unencrypted SSH key for SSH endpoint testing. Closes #1257 . I don't know if I should be adding a separate test for private-key, please let me know if I should :)

Checklist

  • Tested and/or added tests to validate that the changes work as intended, if applicable.
  • Updated documentation in README.md, if applicable.

@github-actions github-actions bot added the feature New feature or request label Nov 16, 2025
@TwiN TwiN changed the title feat(endpoint): Add ssh key support feat(client): Add ssh private-key support Nov 16, 2025
@TwiN
Copy link
Owner

TwiN commented Nov 16, 2025

Excellent work! I'd appreciate a test for the private key, as you've suggested, though, and then we're good to go! No need to make it super complex.

@mufeedali
Copy link
Contributor Author

mufeedali commented Nov 17, 2025

I looked into what we could be testing here. I've added a few cases to the existing config testing. But I can't think of a way to implement proper integration testing. Password-only could maybe be verified using https://test.rebex.net/ but can't think of a decent way to test private key auth.

@mufeedali
Copy link
Contributor Author

@TwiN I think the tests failed due to GitHub facing issues. Could you try re-running the tests?

@TwiN TwiN merged commit 6f9db41 into TwiN:master Nov 19, 2025
2 of 3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

feature New feature or request

Projects

None yet

Development

Successfully merging this pull request may close these issues.

No option for SSH key

2 participants