Skip to content

fix(pty): use OpenSSL crypto backend on Windows for curve25519 KEX #78

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.

Sign up for GitHub

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

Open
srstack wants to merge 1 commit into
base: main
Choose a base branch
from
Open

fix(pty): use OpenSSL crypto backend on Windows for curve25519 KEX #78

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 4 additions & 1 deletion otty-pty/Cargo.toml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -15,7 +15,10 @@ anyhow = { workspace = true }
thiserror = { workspace = true }
log = { workspace = true }
mio = { workspace = true, features = ["os-ext", "net"] }
ssh2 = "0.9.5"
# `openssl-on-win32`: make the Windows build use the (vendored) OpenSSL
# crypto backend instead of WinCNG. WinCNG offers only finite-field DH key
# exchange, which modern servers (OpenSSH >= 10) no longer accept.
Comment on lines +18 to +20
ssh2 = { version = "0.9.5", features = ["openssl-on-win32"] }
# Force a statically-linked (vendored) OpenSSL build. The `ssh2` crate pulls in
# `libssh2-sys` -> `openssl-sys`, which by default links the host's libssl.
# Different Ubuntu releases ship incompatible sonames (libssl1.1 on 20.04,
Expand Down