Windows 10: sftp by OpenSSH server on windows 10 doesn't work with multiple drives.

I have an openssh server set up on my windows machine. I set up this for the sftp purpose.the trouble is, I cannot access two drives at the same time.At first the sftp would be at the c-drive. but the primary contents that i wanted to access was in E:, and It seemed impossible to reach e:. so I edited the sshd_config so the chroot directory at e:\Second problem is that I also have the secondary contents on my s-drive. So I created a symlink on e:\ that would direct me to s-drive's contents. However, it didn't work, and i couldn't get the contents.It turns out that what actually matters is that

:)

 

How to add/remove drives to Windows OpenSSH SFTP server?

While some Windows SFTP servers do implement a virtual root folder which lists available drives, Win32-OpenSSH does not. It redirects the root folder / to /C:/ (or maybe to a system drive).

If you want to visit another drive, you have to manually change a working directory.

• In WinSCP GUI, you can do that using "Open Directory" command and typing a path to the desired drive, like /D:/.
  
• In command-line SFTP clients, like OpenSSH sftp, PuTTY psftp or WinSCP scripting, you can use cd command, like:
  
  

There's actually WinSCP FAQ for How do I change drive on the remote panel?

Regarding your attempt to solve this using a symlink: A symlink really shows as a file in WinSCP (as the server presents it as an unknown file type). But a directory junction shows as a directory (the server presents it as a regular directory, not a link).

 

Windows doesn`t start. Authomatic repair doesn`t work.

Thanks again!!

I`m sorry I had not noticed that the text on the picture was in spanish. It says that windows has replaced some damaged clusters in "name" file and "directory". Then, at the end "an unspecified error occurred (75736e6a726e6c2e 4f6)".

I`ll do it and I`ll be updating this thread when I have the report.

- - - Updated - - -

I ran SeaTools. These are the results:




Does it mean my HDD is useless?

 

OpenSSH Key based auth doesn't work as expected

I was testing sftp using openssh for a while now. I tested password based authentication with key based, which means the user who wants to login should provide his private key when trying to connect with the sftp server(openssh). If he had a valid private key then key will be prompted to enter his password. Only if those two authentications were successfully done, the user will get the permission to access the server.

The problem i witnessed is the following(open the sshd_config file):

• My Standard Authentication method is passwrod based
  
  • #PubkeyAuthentication no
    
  • PasswordAuthentication yes
    
• I activated for two users password based authentication with key based
  
  • Match User userA,userB
    
  • AuthenticationMethods publickey,password
    
  • Match all
    
• It works perfectly.
  
  • sftp -i C:\User\userA\keys\id_ras *** Email address is removed for privacy ***
    
• Then i decided to deactivate this (by putting # in front of the command) and set for those users only password based authentication which is set as standard for sftp connections to the server.
  
  • #Match User userA,userB
    
  • #AuthenticationMethods publickey,password
    
  • #Match all
    
• From now on i expect that the users "userA" & "userB" can only access the server by using their password. Even if they give their private key while trying to connect, the private key should not be relevant.
  
• But unfortunately the users can connect to the server either using only the private key or only the password. The reason is that with "#" key based won't be deactivated but it's like the server saying that "i don't know if public key is allowed or not but if a user comes up with his private key and his public key is linked in his user folder on this server then he can use either ways".
  
• If i really don't want this to happen then i have to either set pubkeyauthetication to no without #
  
  • PubkeyAuthentication no
    
• Or i have to leave this #PubkeyAuthentication no but therefore remove the public key link in the users folder on the server.
  

Now i would love to know, if there is any possibilities to do this only in the configuration file without having to remove the link in the users folder on the sftp server?