-
Notifications
You must be signed in to change notification settings - Fork 1.3k
dulwich: fallback to default SSH keys in asyncssh vendor #6983
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. Weβll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
|
@dberenbaum @karajan1001 can you try this patch to confirm it allows you to push/list exps from github? Also please note what type of SSH keys you are using (RSA or ed25519) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should note that this appears to be specific to github. gitlab's SSH server returns the proper algorithm names in the auth responses.
This is also one of those cases where the RFC's do note that some existing SSH implementations in the wild may just always use "ssh-rsa", and that it's up to individual client/server implementations to decide whether or not to allow or reject those requests & responses.
|
My result |
446f212 to
5b7f2d3
Compare
|
@karajan1001 please try the latest version of the PR and see if it resolves the push issue |
|
Works with my keys, at least. |
|
It works for me only if I have an empty passphrase. With a passphrase set, I get: |
|
@dberenbaum are you normally prompted for your passphrase when you
|
No.
My I also tried with an rsa key and got the same error. |
Works for me now. |
|
@dberenbaum the passphrase issue should be resolved in the latest version of this PR |
7ce23db to
fc6229b
Compare
- vendor should use ssh-agent or default IdentityFile(s) when no SSH key has been provided by the user - encrypted (fallback) keys will always be passed to ssh-agent
- allow mismatched RSA signature algo names in initial SSH_MSG_USERAUTH_PK_OK response - unit test overridden asyncssh publickey auth compatibility with github ssh server
fc6229b to
6c3adba
Compare
|
This is ready for review but shouldn't get merged until there's a new sshfs release w/the updated asyncssh dependency version |
|
sshfs 2021.11.1 is out |
|
Nice! It works now, thanks. Comment on rebasing: I went to look for what was changed to fix my earlier issues, but I can't tell anymore. Not a big deal. |
It was originally a separate commit in the PR, but it was a small one-line change that fit better into aca229a so I squashed it in the final PR changeset (the specific change is the inclusion of |
β I have followed the Contributing to DVC checklist.
π If this PR requires documentation updates, I have created a separate PR (or issue, at least) in dvc.org and linked it here.
Thank you for the contribution - we'll try to review it as soon as possible. π
Will fix #6920
Related to #2215