-
Notifications
You must be signed in to change notification settings - Fork 389
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
ssh_key_from_memory no longer respected #363
Comments
Oh oops, sorry about this! I was assuming that we'd always be building libssh2 from source (erroneously) and was looking to remove the opt-in needed for this API. Would it be possible to build libssh2 bundled like you're buliding libgit2 bundled? |
I guess so, but where does that end? In any case having the ssh_key_from_memory there but ignored definitely doesn't seem right! It seems very easy to respect it, I guess I can add a patch for that if you'd be willing to take it. PS: sorry for the slow reply! |
Oh sure yeah, either way's fine by me! |
It's been a while and no one seems to have missed having the option to disable |
The ssh_key_from_memory crate feature was added in commit 8ca0e92 (2018-07-26). Then it was accidentally made always-on in commit 76f4b74 (2018-09013). Since it seems like no one has missed the ability to turn it off since then (not enough to send a PR anyway), let's just delete the crate feature. Closes rust-lang#363
(Disclaimer: I'm very new at this)
It seems to me that one of the side effects of alexcrichton@76f4b74#diff-612b86ed90c06a3454760b47abd89aea was that the ssh_key_from_memory feature is no longer checked independently of the ssh feature, i.e. GIT_SSH_MEMORY_CREDENTIALS is always defined if GIT_SSH is. This broke my backport of cargo to an older release of Ubuntu where libssh2 is a bit old.
The text was updated successfully, but these errors were encountered: