consider renaming internal ssh.exe to prevent sshfs-win picking up system tool with the same name
Open
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 6.4k
- Forks
- 315
- PR merge metrics
- No merged PRs in 30d
Description
A SiriKali user just reported sshfs-win picking ssh.exe executable installed on the system and not the private copy shipping with sshfs-win and this could cause hard to debug issues.
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 reading the linked SiriKali reports and tracing where sshfs-win packages, locates, and invokes its private ssh.exe. No source file or test is named in the issue. Done means the bundled executable no longer collides with a system ssh.exe and all affected references continue to work.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100