PowerShell / PowerShell/Win32-OpenSSH
Win32-OpenSSH fails to use network mapped directory
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 8.3k
- Forks
- 819
- PR merge metrics
- No merged PRs in 30d
Description
Prerequisites
- Write a descriptive title.
- Make sure you are able to repro it on the latest version
- Search the existing issues.
Steps to reproduce
Running OpenSSH on Windows Server 2016. Using Renci.SSHNet as sftp client. Trying to use Renci SSHNet SFTP to transfer files to a directory share on the OpenSSH server.
ChrootDirectory /FileDrop
doesn't work.
Nor does //FileDrop
Nor does /
and then using SFTP to change to /FileDrop or //FileDrop
How to use a mapped network directory e.g. c:\AllDroppedFiles shared as /FileDrop ? OpenSSH service will not even start when ChrootDirectory in sshd_config file is set to /FileDrop or //FileDrop etc
Only paths I can get to work seem to be true paths on a drive e.g. c:\AllDroppedFiles will work.
Expected behavior
shared network directory works e.g. on OpenSSH server user has permissions to network share
Actual behavior
No such file error - cannot drop to network shared directory
Error details
No such file
Environment data
9OpenSSH_9.4p1 for Windows
Version
OpenSSH_9.4p1 for Windows
Visuals
No response
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
Reproduce the failure on Windows Server 2016 using sshd_config with ChrootDirectory /FileDrop and a mapped c:\AllDroppedFiles network share, then compare it with a local drive path. Start with the ChrootDirectory handling and service startup diagnostics; done means a mapped directory works through SFTP or the limitation and required configuration are documented.
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
- 30/100