Block when connecting to a host with authorized_keys
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 566
- Forks
- 163
- Avg merge
- 4h 51m
- Merged PRs (30d)
- 2
Description
Calling Session::handshake(&self) block forever for a remote host with a public key listed on .ssh/authorized_keys.
I assume calling Session::handshake(&self) should be enough to authenticate since in a normal shell it doesn't require a password. Is this the right way to do or supported use case?
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the reported Session::handshake(&self) call in ssh2-rs and reproduce the block when the remote host has a key in .ssh/authorized_keys. Determine whether handshake alone is expected to authenticate in this case, and use that finding to define whether the fix should address the behavior or clarify the supported use case.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- networking
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100