Lib.rs

› Network programming | Cryptography
#libssh #bindings #openssl #likely #user #couple #vendored-openssl

libssh-rs

Bindings to the libssh library

by Wez Furlong and 5 contributors

12 releases

0.2.2 Oct 30, 2023
0.2.0 May 30, 2023
0.1.8 Mar 29, 2023
0.1.4 Jan 31, 2022
0.1.1 Nov 14, 2021

#593 in Network programming

Download history 906/week @ 2023-12-13 715/week @ 2023-12-20 706/week @ 2023-12-27 1077/week @ 2024-01-03 1142/week @ 2024-01-10 2365/week @ 2024-01-17 2304/week @ 2024-01-24 2052/week @ 2024-01-31 1273/week @ 2024-02-07 1060/week @ 2024-02-14 908/week @ 2024-02-21 899/week @ 2024-02-28 785/week @ 2024-03-06 804/week @ 2024-03-13 1053/week @ 2024-03-20 645/week @ 2024-03-27

3,390 downloads per month
Used in 4 crates (via wezterm-ssh)

MIT license

3.5MB
88K SLoC

C 83K SLoC // 0.1% comments Rust 5K SLoC // 0.0% comments Shell 110 SLoC // 0.1% comments C++ 42 SLoC // 0.4% comments JavaScript 19 SLoC // 0.2% comments Python 8 SLoC

libssh-rs

Build Status Build Status Build Status

Bindings to libssh.

Features

The vendored feature causes a static version of libssh to be compiled and linked into your program. If no system libssh is detected at build time, or that system library is too old, then the vendored libssh implementation will be used automatically. Note that the libssh-rs bindings make use of a couple of new interfaces that have not made it into a released version of libssh at the time of writing this note, so all users will be effectively running with vendored enabled until libssh releases version 0.9.7.

The vendored-openssl feature causes a vendored copy of openssl to be compiled and linked into your program.

On macOS and Windows systems, you most likely want to enable both vendored and vendored-openssl.

License

This crate is licensed under the MIT license, and is:

Copyright (c) 2021-Present Wez Furlong.

Dependencies

~0.7–2.5MB
~53K SLoC