Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.
Sign upAdd multiple features, bug fixes and update libssh2 to the latest stable. #94
Conversation
This enables giving ssh a prefered list of options such as kex, ciphers, MACs and etc
Add libsssh2_session_method_pref
Add recompiled cython files
Regenerate Cython files. Add `ssh2.session.Session.method_pref()` doc string. Update .gitignore to include src directory to ignore libssh2 rebuilds.
Add additional error codes. Add `session.method_pref()` docs and tests. Add `session.methods()`, docs and tests. Add `session.supported_algs()`, docs and tests. Add `session.flag()`, docs and tests. Bug fix for `session.userauth_publickey_frommemory()` being provided no public key and throwing a type error.
Add callback function typedef for keyboard interactive authentication. Add `ctypedef`s for keyboard interactive authentication. Fix keyboard interactive authentication function def in c_ssh. Internally hide that `libssh2_userauth_keyboard_interactive` takes a callback function and not a string...
Correct issue in `ssh2.sftp_handel.SFTPHandle.readdir*()` which adds EAGAIN items into the generators.
Rename library to redlibssh2.
llchan
commented
Jun 29, 2020
|
Thanks for splitting off dedicated PR branch. Could you revert the changes that rename |
|
Ah bugger, I did not see the 2nd line on that commit message, haha. |
fruch
commented
Jul 20, 2020
|
seems like appveyor isn't happy
May I suggest trying to move to travis ? (they now support windows and mac) |
|
@llchan @fruch |
fruch
commented
Jul 26, 2020
FYI you can build on travis for multiple platfrom quite easily with cibuildwheel It's breaks my heart to see those kind of failures.... |
|
Thanks for the PR. Have made similar changes, will aim to get these in. If @Red-M is interested can add you to this project. As has been obvious from this PR, there is only so much one maintainer can do. |
|
| Thanks for splitting off dedicated PR branch. Could you revert the changes that rename ssh2 to redlibssh2 in this branch? I assume the maintainer(s) will require that before it can be merged. Yes. |
|
| I'll be happy to give a hand with such a setup if you want [cibuildwheel] @fruch , if you would like to take a stab at re-doing the wheel builds for travis CI would welcome a PR. |
| @@ -0,0 +1,3 @@ | |||
| [submodule "libssh2"] | |||
This comment has been minimized.
This comment has been minimized.
pkittenis
Aug 12, 2020
Member
Would rather not use submodules. It adds quite a bit of overhead on the developer and can be confusing to work with. The source code is included in the repo so as not to have to use submodules.
This comment has been minimized.
This comment has been minimized.
Red-M
Aug 12, 2020
•
Author
I'd prefer to use git submodules as they're designed to do this very thing for tracking a particular remote's branch.
In this PR I've told it to track the 1.9.0 release commit from libssh2's tags/release on github.
All this needs is some work on putting git hooks into the repo with some minor bash scripts. (If libssh2 ever get around to releasing another version that is).
This way we could say switch to a repo of our own choosing for builds if libssh2 doesn't take a patch or is slow to respond to a security issue. It also provides us with git history as well.
I'd love to do that.
This has already been done in the latest commit. |
|
Closing this so can split the various tasks into different PRs. Libssh2 upgrade is being done in #101 In general better to do one thing per PR to make reviewing easier, eg API implementation, libssh2 upgrade, bug fixes etc. This PR has too many unrelated changes to effectively review at once. |
|
@pkittenis RE:
What would I need to do for this to be done? As far as:
This is a little more difficult than you think as I removed the git commit history that contained LFS objects because it costs money from GitHub to use that and that carrying around packages and installing them is a bad practice instead of letting the OS for the builds handle that. |
Red-M commentedJun 25, 2020
This is a new PR (from #90) to track the branch of changes for upstream as I see it now that I am required to make my own changes and publish under a new name as it appears the maintainer has disappeared.
The changes are as follows. I also recommend reading the commit messages and the changes on each commit instead of the roll up diff as it is HUGE.
Changes