winfsp / winfsp/sshfs-win

Null character after drive letter when using sshfs.r or sshfs.kr and seems to interfere causing access denied

Open
#458 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
C
Stars
6.4k
Forks
315
PR merge metrics
No merged PRs in 30d

Description

I am trying to use winfsp with a Windows 2019 server running OpenSSH. A null character is showing up after the drive letter and seems to interfere with accessing folders and files.

Used a hex editor and can see the character is \0 or 0 or null.

The sshd.exe version is 7.7.2.2

Tried this with Server 2012 running sshd.exe version 9.8.1.0 and seeing the same thing

The client OS version:
Edition Windows 11 Pro
Version 23H2
Installed on ‎5/‎11/‎2023
OS build 22631.5039
Experience Windows Feature Experience Pack 1000.22700.1074.0

winfsp installation:w

C:\Windows\System32\WindowsPowerShell\v1.0> winget install SSHFS-Win.SSHFS-Win
Found SSHFS-Win [SSHFS-Win.SSHFS-Win] Version 3.5.20357
This application is licensed to you by its owner.
Microsoft is not responsible for, nor does it grant any licenses to, third-party packages.
This package requires the following dependencies:
  - Packages
      WinFsp.WinFsp
(1/1) Found WinFsp 2023 [WinFsp.WinFsp] Version 2.0.23075
This application is licensed to you by its owner.
Microsoft is not responsible for, nor does it grant any licenses to, third-party packages.
Downloading https://github.com/winfsp/winfsp/releases/download/v2.0/winfsp-2.0.23075.msi
  ██████████████████████████████  2.10 MB / 2.10 MB
Successfully verified installer hash
Starting package install...
Successfully installed

Downloading https://github.com/billziss-gh/sshfs-win/releases/download/v3.5.20357/sshfs-win-3.5.20357-x64.msi
  ██████████████████████████████  4.85 MB / 4.85 MB
Successfully verified installer hash
Starting package install...
Successfully installed
C:\Windows\System32\WindowsPowerShell\v1.0>

Image

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Reproduce the reported access-denied behavior with the listed Windows, WinFsp, SSHFS-Win, and OpenSSH versions, using the installation command and screenshot as reference. No source file or test is named; done would be identifying the cause of the null character after the drive letter and verifying that file and folder access works without it.

Written by the indexing model from the issue text.

Assessment

Domain
networking, operating-systems
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.