[Feature Request] API for checking whether authentication method failed because of mem/protocol error or is rejected by the server
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 566
- Forks
- 163
- Avg merge
- 4h 51m
- Merged PRs (30d)
- 2
Description
I have just briefly through the doc of ssh2-rs and libssh2 and it seems that authentication in libssh2 can failed due to netework issues, run out of memory, etc.
However, it is actually hard to tell that in ssh2-rs due to the lack of API in Error for that.
This API is necessary when the program need to try multiple authentication methods.
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 by reviewing the ssh2-rs Error API and the libssh2 authentication errors described in the issue. Determine how callers can distinguish protocol, network, or memory failures from server rejection, then add an API whose behavior is covered by focused tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- api, authentication
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100