Preferred keys negotiation order
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 9.9k
- Forks
- 2.1k
- PR merge metrics
- No merged PRs in 30d
Description
I was wondering how we arrived at this preferred keys order?
It does not correspond to that of OpenSSH's client, so I was wondering why?
Thank you.
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 paramiko/transport.py lines 172-177 and compare the preferred key order there with the OpenSSH client order referenced in the issue. The issue does not define whether the desired outcome is an explanation, documentation, or a change, so completion depends on agreeing on that scope first.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- networking
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100