sftp by OpenSSH server on windows 10 wouldn't be able to access another drive.

Question

sftp by OpenSSH server on windows 10 wouldn't be able to access another drive.

Junseo Park 20

https://answers.microsoft.com/en-us/windowsclient/forum/all/sftp-by-openssh-server-on-windows-10-doesnt-work/8df305c6-c4df-4e0a-ac64-1055979c2da4 I asked a question on somewhere else and they told me to come here and ask questions, so here i am. haha hi! Basically I was told that OpenSSH doesn't really work on multiple drives But that's strange, because it used to work just a few days ago in my old windows OS on my system before i set up a new windows OS this weekend. I set it up so that the chroot directory is on e-drive and created a symbolic link to access another folder in s-drive to make it work. But the openSSH on the new system wouldn't be able access contents from the s-drive but only from the e-drive. Although, this new windows system became uefi/gpt instead of the bios/mbr. probably that was the reason why OpenSSH stopped working on multiple drives. Anyways, does anybody know how to make this OpenSSH from the windows 10 work on multiple drives? or should I have multiple sftp servers for each drive? or another SSH server from a third party would work the way I want it? It's been only 3 days and I already dont like gpt... maybe i should've stayed with mbr......................

Accepted answer

1 additional answer

Your answer

Answer 1

MotoX80 36,401

Got it. The ChrootDirectory statement is jailing the user to just that drive/folder.

I defined 3 user accounts to test with. Here are the relevant sshd_config statements.

# Authentication:
Allowusers testuser*

# ForceCommand internal-sftp 
Subsystem	sftp	sftp-server.exe


Match user testuser2
       ChrootDirectory e:/
Match user testuser3
       ChrootDirectory C:/Temp

Here is the first user. It sees all of the drives and can access files in e:\Data. Note the directory names. User's image

The second user is jailed to the E: drive. User's image

The 3rd user is jailed to c:\temp. User's image

If you only want to have one user, then remove the chroot for it. If you need to jail the sftp accounts, then you will need 2 user accounts, one for E drive and one for the S drive. https://www.bing.com/search?q=sshd_config+ChrootDirectory+jail+windows

Junseo Park 20 Reputation points

2024-02-14T00:41:35.2733333+00:00

0I went on to a vacation right after i posted this question, and i read your writing immediately. the reason why i couldn't comment you back is because this problem was home while i was away. haha i commented out the chroot line from sshd_config as you suggested, and it worked like a charm. Thank you.

Answer 2

MotoX80 36,401

created a symbolic link to access another folder in s-drive to make it work. But the openSSH on the new system wouldn't be able access contents from the s-drive

What error do you get? Did you check the NTFS permissions?

This worked for me on my E drive (ChrootDirectory) to access the temp folder on C.

mklink /d CTemp c:\temp

Junseo Park 20 Reputation points

2024-01-31T02:13:44.0666667+00:00

That mklink command is exactly what i did haha. But its not working for me. As soon as i go across the inter-drive symbilic link, i'd get 'permission denied' error message when i try to read the contents of the file. I think the permission is just fine. 1 i am fairly sure that i set it up correctly. 2 i can access the same file that was denied a second ago if i change the sshd_config of the ssh server and change the drive letter of the chroot directory. If the s-drive is the chroot then s-drive is accessible, and e-drive is accessible only when sshd_config says e:/ is its chroot.
MotoX80 36,401 Reputation points

2024-01-31T13:34:04.11+00:00

I think that I managed to recreate your error. Let me see if I can find a workaround.

Share via

sftp by OpenSSH server on windows 10 wouldn't be able to access another drive.

1 additional answer

Your answer