Thrussh

A full implementation of the SSH 2 protocol, both server-side and client-side.

Thrussh is completely asynchronous, and can be combined with other protocols using Tokio.

Contributing

We welcome contributions. Currently, the main areas where we need help are:

• Handling SSH keys correctly on all platforms. In particular, interactions with agents, PGP, and password-protected/encrypted keys are not yet implemented.

• Auditing our code, and writing tests. The code is written so that the protocol can be entirely run inside vectors (instead of network sockets).

By contributing, you agree to license all your contributions under the Apache 2.0 license.

Moreover, the main platform for contributing is the Nest, which is still at an experimental stage. Therefore, even though we do our best to avoid it, our repository might be reset, causing the patches of all contributors to be merged.

Issue Reporting

Please report bugs on the issue page of this repository. Thrussh has a full disclosure vulnerability policy. Please do NOT attempt to report any security vulnerability in this code privately to anybody.

Redox Porting Notes

Please add to this section with anything you'd like others to know if you contribute to this port.

• All deps have been taken care of. In order to compile for redox, openssl and libsodium must be set up on your system for redox building. I really have no idea how this works, there is a cookbook recipe for libsodium that works fine (I think), so clone this repo into a cookbook recipe source/ and add this to your recipe.sh:

BUILD_DEPENDS=(openssl libsodium)

• There are four crates in this repository, 3 of them build under redox: thrussh, thrussh-keys, and thrussh-libsodium. The fourth, thrussh-agent, depends on Unix specific features (sockets) that are not yet implemented to an adequate degree on Redox. It also requires two functions to be added to liblibc, and probably has a dependency issue. Kudos if anybody fixes this.