Skip ssh config parsing when Net::OpenSSH backend is used
Nobody has claimed this yet.
- Dominant language
- Perl
- Stars
- 737
- Forks
- 214
- PR merge metrics
- No merged PRs in 30d
Description
Net::OpenSSH backend just uses the OpenSSH binaries in the backgrond, so they should be able to transparently use any available ssh configuration like ~/.ssh/config.
So in that case, there's no need to try and parse the ssh configuration, but we should make sure it still works for other backend that might rely on it (like Net::SSH2).
Contributor guide
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 locating the SSH configuration parsing path and the backend-selection logic, then compare how the Net::OpenSSH and Net::SSH2 backends use configuration data. Verify that Net::OpenSSH can rely on the OpenSSH binaries and that other backends still receive parsed configuration; add or update tests covering both backend paths.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- perl
- Domain
- backend, infrastructure
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100