Skip to content

treewide: Migrate to russh#10

Merged
konradybcio merged 1 commit into
linux-msm:masterfrom
quic-kdybcio:topic/russh
Nov 7, 2025
Merged

treewide: Migrate to russh#10
konradybcio merged 1 commit into
linux-msm:masterfrom
quic-kdybcio:topic/russh

Conversation

@quic-kdybcio
Copy link
Copy Markdown
Contributor

russh doesn't have the libsodium compilation issues on Windows that ssh2 - migrate to it.

russh doesn't have the libsodium compilation issues on Windows that
ssh2 - migrate to it.

Signed-off-by: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
Copy link
Copy Markdown

@andersson andersson left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This does solve my problem of the current implementation being an async API ontop of sync operations - which obviously didn't do what I expected.

I think the API can be made a bit more ergonomic, but that can be done as a follow up.

Comment thread cli/src/main.rs
let mut sess = ssh_connect(args.farm, args.port, args.user).await?;
sess.set_blocking(true);
let mut chan = ssh_get_chan(&mut sess, CDBA_SERVER_BIN_NAME).await?;
let chan = Arc::new(Mutex::new(
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The only reason I can see for this being an Arc<Mutex<Channel>> and not just a Channel is because ssh::into_streams() below takes a Arc<Mutex<>>, presumably so that one could share the chan with the close at the async thread?

I think it would be cleaner if sk8brd provided an interface that abstracts away the ssh_connect() and just returns the three streams.

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm merging this as-is, we can make incremental improvements

@konradybcio konradybcio merged commit b1237dc into linux-msm:master Nov 7, 2025
5 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants