wezterm/wezterm-ssh/Cargo.toml

[package]
name = "wezterm-ssh"
version = "0.3.1"
authors = ["Wez Furlong <wez@wezfurlong.org>"]
edition = "2018"
repository = "https://github.com/wez/wezterm"
description = "More convenient higher level wrapper around libssh2"
license = "MIT"
documentation = "https://docs.rs/wezterm-ssh"

# See more keys and their definitions at https://doc.rust-lang.org/cargo/reference/manifest.html

[features]
vendored-openssl = ["ssh2/vendored-openssl", "libssh-rs/vendored-openssl"]

[dependencies]
anyhow = "1.0"
base64 = "0.13"
bitflags = "1.3"
camino = "1.0"
dirs-next = "2.0"
filedescriptor = { version="0.8", path = "../filedescriptor" }
filenamegen = "0.2"
libc = "0.2"
log = "0.4"
portable-pty = { version="0.7", path = "../pty" }
regex = "1"
smol = "1.2"
ssh2 = {version="0.9.3", features=["openssl-on-win32"]}
libssh-rs = {version="0.1.2", features=["vendored"], git="https://github.com/wez/libssh-rs.git"}
#libssh-rs = {path="../../libssh-rs/libssh-rs", features=["vendored", "vendored-openssl"]}
thiserror = "1.0"

# Not used directly, but is used to centralize the openssl vendor feature selection
async_ossl = { path = "../async_ossl" }

[dev-dependencies]
assert_fs = "1.0.4"
indoc = "1.0"
k9 = "0.11.0"
once_cell = "1.8"
predicates = "2.0"
pretty_env_logger = "0.4"
rstest = "0.12"
shell-words = "1.0"
smol-potat = "1.1.2"
structopt = "0.3"
termwiz = { version = "0.14", path = "../termwiz" }
whoami = "1.1"
Add ssh_config parser refs: https://github.com/wez/wezterm/issues/457 2021-03-16 19:43:33 +03:00			`[package]`
			`name = "wezterm-ssh"`
Pick up updated ssh crate + windows fixes 2021-12-11 01:25:48 +03:00			`version = "0.3.1"`
Add ssh_config parser refs: https://github.com/wez/wezterm/issues/457 2021-03-16 19:43:33 +03:00			`authors = ["Wez Furlong <wez@wezfurlong.org>"]`
			`edition = "2018"`
prep for wezterm-ssh release This temporarily disables the win32 openssl build stuff; need https://github.com/alexcrichton/ssh2-rs/pull/216 to land before this package can publish with that feature. 2021-04-30 20:27:39 +03:00			`repository = "https://github.com/wez/wezterm"`
			`description = "More convenient higher level wrapper around libssh2"`
			`license = "MIT"`
			`documentation = "https://docs.rs/wezterm-ssh"`
Add ssh_config parser refs: https://github.com/wez/wezterm/issues/457 2021-03-16 19:43:33 +03:00
			`# See more keys and their definitions at https://doc.rust-lang.org/cargo/reference/manifest.html`

Expose vendored-openssl feature of ssh2 from wezterm-ssh 2021-09-21 21:57:49 +03:00			`[features]`
ssh: fixup vendored-openssl selection for libssh-rs 2021-10-20 06:18:14 +03:00			`vendored-openssl = ["ssh2/vendored-openssl", "libssh-rs/vendored-openssl"]`
Expose vendored-openssl feature of ssh2 from wezterm-ssh 2021-09-21 21:57:49 +03:00
Add ssh_config parser refs: https://github.com/wez/wezterm/issues/457 2021-03-16 19:43:33 +03:00			`[dependencies]`
wezterm-ssh: flesh out improved ssh crate This implementation should be less prone to stutters/stalls than my earlier hacky implementation in pty/src/ssh.rs 2021-03-19 18:07:44 +03:00			`anyhow = "1.0"`
			`base64 = "0.13"`
Add bitflags type safety to sftp flags 2021-10-03 23:37:19 +03:00			`bitflags = "1.3"`
Switch to camino::{Utf8PathBuf, Utf8Path} 2021-10-04 04:36:30 +03:00			`camino = "1.0"`
Add ssh_config parser refs: https://github.com/wez/wezterm/issues/457 2021-03-16 19:43:33 +03:00			`dirs-next = "2.0"`
filedescriptor: remove anyhow from public interface Use thiserror instead 2021-05-24 00:24:01 +03:00			`filedescriptor = { version="0.8", path = "../filedescriptor" }`
wezterm-ssh: process Include statements refs: https://github.com/wez/wezterm/issues/824 2021-05-29 07:30:26 +03:00			`filenamegen = "0.2"`
ssh: can now pass e2e tests using libssh backend 2021-10-19 19:19:33 +03:00			`libc = "0.2"`
wezterm-ssh: flesh out improved ssh crate This implementation should be less prone to stutters/stalls than my earlier hacky implementation in pty/src/ssh.rs 2021-03-19 18:07:44 +03:00			`log = "0.4"`
pty: introduce ChildKiller trait In the mux layer, we have some code that takes a `Child` and then does a bit of naughty reaching through the abstraction to get at the pid/handle of the child so that we can send it signals even if the child is itself mutably (and thus exclusively) borrowed for the purposes of waiting. That worked fine for local processes spawned in the mux, but we also use LocalPane to wrap around arbitrary `Child`ren, such as Ssh, that are not local and that don't have a local process id, which meant that this hack wouldn't work for them. To make things a bit worse, those ssh ptys were used to ssh2 days where we didn't have a way to signal the remote process and just did nothing, leading to confusing situations such as https://github.com/wez/wezterm/issues/1197 This commit graduates the hack mentioned in the first paragraph to its own ChildKiller trait. This makes the concept of waiting for the Child distinct from signalling it and explicitly allows getting a separate object that can be used for signalling. With that in place, we're forced to implement something appropriate for the ssh pty implementations; one in the pty crate itself, one in wezterm-ssh and the wrapper that we use in the mux crate. The upshot of this is that the `CloseCurrentPane` action now operates correctly on panes that were the result of split operations. 2021-12-11 18:32:21 +03:00			`portable-pty = { version="0.7", path = "../pty" }`
Add ssh_config parser refs: https://github.com/wez/wezterm/issues/457 2021-03-16 19:43:33 +03:00			`regex = "1"`
wezterm-ssh: flesh out improved ssh crate This implementation should be less prone to stutters/stalls than my earlier hacky implementation in pty/src/ssh.rs 2021-03-19 18:07:44 +03:00			`smol = "1.2"`
ssh: my openssl+windows ssh2 patch was published upstream So remove my local patch 2021-10-10 17:29:54 +03:00			`ssh2 = {version="0.9.3", features=["openssl-on-win32"]}`
fix windows build A recent cargo update caused openssl-sys to do a minor semver update from 0.9.71 -> 0.9.72, but that release downgraded from openssl 3 to openssl 1 to resolve a performance regression: <https://github.com/sfackler/rust-openssl/pull/1578> That in turn caused libssh to fail to build because the ENGINE feature required by libssh isn't compiled in in openssl-src 1 crate when vendoring on windows. For now, my libssh git repo is constrained to openssl-sys 0.9.71, and we're pointing to that from the wezterm repo. 2021-12-13 19:00:13 +03:00			`libssh-rs = {version="0.1.2", features=["vendored"], git="https://github.com/wez/libssh-rs.git"}`
Run with libssh This works, but on macOS, there is a segfault in openssl when the session is closed... I'm going to try this on Linux to see if it is consistent behavior and ponder next steps. 2021-10-18 16:55:01 +03:00			`#libssh-rs = {path="../../libssh-rs/libssh-rs", features=["vendored", "vendored-openssl"]}`
Create SftpError type and associated structs to provide more verbose errors for sftp 2021-09-27 04:54:08 +03:00			`thiserror = "1.0"`
Add ssh_config parser refs: https://github.com/wez/wezterm/issues/457 2021-03-16 19:43:33 +03:00
weird dependency hack for mac+windows Adding an edge from wezterm-ssh -> async_ossl causes the openssl vendoring feature selection logic to trigger, which in turn allows `cargo build -p window --examples` to succeed again on macos. 2021-07-10 06:34:42 +03:00			`# Not used directly, but is used to centralize the openssl vendor feature selection`
restore async_ossl dep after wezterm-ssh crates.io release 2021-11-23 15:36:52 +03:00			`async_ossl = { path = "../async_ossl" }`
weird dependency hack for mac+windows Adding an edge from wezterm-ssh -> async_ossl causes the openssl vendoring feature selection logic to trigger, which in turn allows `cargo build -p window --examples` to succeed again on macos. 2021-07-10 06:34:42 +03:00
Add ssh_config parser refs: https://github.com/wez/wezterm/issues/457 2021-03-16 19:43:33 +03:00			`[dev-dependencies]`
Add some initial tests to wezterm-ssh, ignoring read/write of file as those are hanging 2021-09-24 21:57:05 +03:00			`assert_fs = "1.0.4"`
Create SftpError type and associated structs to provide more verbose errors for sftp 2021-09-27 04:54:08 +03:00			`indoc = "1.0"`
update k9 to 0.11.0 to make it work with rustc@1.51.0 1.51.0 no longer takes non string literals in `panic()`. k9@0.11.0 fixes that 2021-03-25 20:32:31 +03:00			`k9 = "0.11.0"`
Create SftpError type and associated structs to provide more verbose errors for sftp 2021-09-27 04:54:08 +03:00			`once_cell = "1.8"`
			`predicates = "2.0"`
wezterm-ssh: add pubkey based auth I can't get this to succeed though; I suspect there may be a lingering bug from libssh2 and/or trailing support for newer openssh features. refs: https://github.com/wez/wezterm/issues/457 2021-03-27 09:54:57 +03:00			`pretty_env_logger = "0.4"`
cargo update and bump rstest to make dependabot happier 2021-12-13 06:21:55 +03:00			`rstest = "0.12"`
wezterm-ssh: flesh out improved ssh crate This implementation should be less prone to stutters/stalls than my earlier hacky implementation in pty/src/ssh.rs 2021-03-19 18:07:44 +03:00			`shell-words = "1.0"`
Add some initial tests to wezterm-ssh, ignoring read/write of file as those are hanging 2021-09-24 21:57:05 +03:00			`smol-potat = "1.1.2"`
wezterm-ssh: flesh out improved ssh crate This implementation should be less prone to stutters/stalls than my earlier hacky implementation in pty/src/ssh.rs 2021-03-19 18:07:44 +03:00			`structopt = "0.3"`
introduce unicode_version config This is a fairly far-reaching commit. The idea is: * Introduce a unicode_version config that specifies the default level of unicode conformance for each newly created Terminal (each Pane) * The unicode_version is passed down to the `grapheme_column_width` function which interprets the width based on the version * `Cell` records the width so that later calculations don't need to know the unicode version In a subsequent diff, I will introduce an escape sequence that allows setting/pushing/popping the unicode version so that it can be overridden via eg: a shell alias prior to launching an application that uses a different version of unicode from the default. This approach allows output from multiple applications with differing understanding of unicode to coexist on the same screen a little more sanely. Note that the default `unicode_version` is set to 9, which means that emoji presentation selectors are now by-default ignored. This was selected to better match the level of support in widely deployed applications. I expect to raise that default version in the future. Also worth noting: there are a number of callers of `unicode_column_width` in things like overlays and lua helper functions that pass `None` for the unicode version: these will assume the latest known-to-wezterm/termwiz version of unicode to be desired. If those overlays do things with emoji presentation selectors, then there may be some alignment artifacts. That can be tackled in a follow up commit. refs: #1231 refs: #997 2021-11-25 18:53:07 +03:00			`termwiz = { version = "0.14", path = "../termwiz" }`
Ensure /run/sshd exists, explicitly set username in sshd fixture, add back use_privilege_mode no 2021-09-27 08:14:06 +03:00			`whoami = "1.1"`