-
Notifications
You must be signed in to change notification settings - Fork 899
SshCredentials API implementation #771
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
Comments
I'm not sure. It seems like it would still be very useful to bind up (I can see punting on |
Is this about talking about what we need or about implementing it? For user/pass, it's exactly the same as what we already have. ssh/libssh2 also has a method called 'keyboard-interactive' which allows you to invert the control flow and have the library call you as long as you don't input the right password. I guess we can implement that too. For keypairs, we would need something similar to what we do in C, a type whose constructor takes in a username, the paths of a keypair and a passphrase for said keypair, and make that function we call internally call Let's not implement The agent bit would be useful if you actually have an agent, which would be true on the unices but probably less so on Windows. There is an extra complication on Windows, which is that people there seem to like using PuTTY for ssh, but libssh2 only deals with openssh-style keys, so I don't know if we can interact with that (the thing to do with git proper is to set your |
The one big missing thing is reading the user's ssh config and acting on it, but there's only so many yaks we can shave. |
I'm getting at the bottom of this. Even though it will be disabled for most users (since we're not building with libssh2), I really need it on MonoDevelop. Will push a branch soon for review. |
@Therzok FYI we just merged something which adds a credential type |
@carlosmn Libssh2 contains some code to support the PuTTY pageant agent on Windows. |
libgit2sharp has support for ssh "certs" and credentials; the shipped libgit2 doesn't due to us not being willing to ship crypto third-party crypto libraries but that's a different issue. |
So, this revolves around implementing SSH interactive only, right?
The text was updated successfully, but these errors were encountered: