feo-cz / win-sshfs Goto Github PK

I'm trying to rename .htaccess.bak to .htaccess.

I get a error window titled "Rename" with text "You must type a filename"

Could you please add a license file, that way I could know how this software can be used.

On waking up the computer from sleep, I get the following exception (using WinSSHFS 1.5.12.8 and Dokany 0.7.3.RC4):

System.NullReferenceException: Odkaz na objekt není nastaven na instanci objektu.
v Sshfs.MainForm.<>c__DisplayClass18.b__16()
v System.Windows.Forms.Control.InvokeMarshaledCallbackDo(ThreadMethodEntry tme)
v System.Windows.Forms.Control.InvokeMarshaledCallbackHelper(Object obj)
v System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
v System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
v System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
v System.Windows.Forms.Control.InvokeMarshaledCallback(ThreadMethodEntry tme)
v System.Windows.Forms.Control.InvokeMarshaledCallbacks()

Currently it is not possible to assign the same drive letter to more than one entry in the connection manager. It is also not possible to add drive letters A: and B: (and perhaps also C:) - even if these drives do not exist as fixed drives in the machine....

Since drive letters are a scarce resource in windows systems it would be preferable to be able to assign the same - perhaps limited to non fixed drive letter to more than one entry.

Nobody (almost) uses floppies any more - I think it must be at least 10 years since I touched a 3-1/2" or 5-1/4 or more than 25 years since I touched an 8 incher...

It will - of course - not be possible to mount an entry if the selected drive letter has already been mounted somewhere - but that is the case if after making the configuration you add another (or 20) hard drive(s) to the system.

I am advocating for letting drive letters be of entirely free choice - or at least make it possible to change it - it might be slightly hidden as for instance in Hold down Shift while opening the Dropdown to get all possible letters. That way the software would allow simple users as well as "hardcore" :-) users.

HC

Running on Win10Pro 64 bit with DokanInstall_0.7.4 and vcredist_x86 (It didnt seem to find the dokan dll with vcredist_x64).
I have also changed the default save position by executing in an elevated command prompt mklink /d C:\Users[username]\AppData\Local\WinSshFS D:\Users[username]\ownCloud\win-sshfs\Config. That way I keep my conf in owncloud for reuse on other computers, though I am sure that the configuration files were not ment for concurrent access. Perhaps it is possible to flush changes to disk at save and monitor conf files for changes... Then again perhaps not :-)

Hi,

Would it be possible to implement keyboard-interactive authentication? I have two use cases, both of which require it at present:

1. The host demands keyboard-interaction and refuses password auth (the prompt is the usual, for a single password).
2. The host prompts for a password, followed by a time-token key.

So Winsshfs would just need to enable this auth mode, then pop a dialog box up with the prompt(s) and accept the response(s).

What do you think?

When I run win-sshfs.exe get the attached error window.

What's strange is that dokan doesn't think anything is mounted:

C:\Program Files (x86)\Dokan\DokanLibrary>dokanctl.exe /v
mounter path C:\Program Files (x86)\Dokan\DokanLibrary\mounter.exe
driver path C:\Windows\system32\drivers\dokan.sys
dokanctl : Aug 21 2015 17:10:55
Dokan version : 740
Dokan driver version : 0x190

C:\Program Files (x86)\Dokan\DokanLibrary>dokanctl.exe /m
mounter path C:\Program Files (x86)\Dokan\DokanLibrary\mounter.exe
driver path C:\Windows\system32\drivers\dokan.sys

C:\Program Files (x86)\Dokan\

Though windows has the Z: drive still showing:

...which can't be ejected:

Also, dokan can't unmount it:

C:\Program Files (x86)\Dokan\DokanLibrary>dokanctl.exe /u Z /f
mounter path C:\Program Files (x86)\Dokan\DokanLibrary\mounter.exe
driver path C:\Windows\system32\drivers\dokan.sys
Unmount failed: ZUnmount status = -1

C:\Program Files (x86)\Dokan\DokanLibrary>

I have an unstable internet connection which might not be helping.
Is there a way I can reset things without rebooting?

Greetings, currently when one starts the WinSshFs program, it is neccessary to manually open the connection dialog.

Please add an option (suggest in the right-click context menu of the tray icon) for "open connect dialog on program start" (not system start / Windows login, but for program start).

I know that there is an option to automatically connect certain drives automatically in a static scenario (example office server), but in scenario where connection to changing different servers is desired, it would be great to have this option - so that connection window opens immediately on program start and I can select server(s) to connect now.

When trying to change the name of a folder on a drive loaded as a network drive, an error saying the file system does not support long names, ssh console has no issue making it happen.

Everytime I built this tool and ran it, I always get this message:

• Dokan v0.7.4
• WinSshFS v.1.5.12.9

I build the project with VS2015 and select Build > Batch Build > Select all Release
Then after it builds, I run WinSshFS > Sshfs > Sshfs > bin > Release > WinSshFS.exe

Full error message

Hi,
I connect to a remote network share using:
Win-sshfs 1.5.12.9-rc1
Dokan 0.7.4
Windows 10 64bit (Surface 3 pro)

Symbolic links are just shown as "files" not as links. I cannot follow these "files" .. so I am stuck in my directory tree ... is that intented this way? Any comments?

best,
Sven

Hi all,

thanks for this awesome piece of software. I ran into an issue when I changed our server from a Ubuntu basis to an openSUSE basis. I had no problems connecting to the old server, but whenever I try to mount the new server I get the "no suitable authentication method" error (see below).
Both putty and WinSCP are able to connect without any issue, and I can mount the drive in my several linux boxes without any problems.
Do you have any idea what might be causing this issue? (the old server is still online and I can mount it without any problems). I'm running Dokany-0.7.4 and win-sshfs. Am I missing some settings? Port 22 is open.

Best regards,
Goetz

Hi dimov,
Is there a possebility that you could share a compiled version?

Thank you! Great work improving win-sshfs

When mounting an Ubuntu instance, and I then shutdown that instance, win-sshfs will crash.

It worked ok for a while, but now I receive the following exception.

The program starts, but when I click on "Show Manager", the main window doesn't appear.

See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.

************** Exception Text **************
System.Xml.XmlException: Unexpected end of file.
at System.Xml.EncodingStreamWrapper.ReadBOMEncoding(Boolean notOutOfBand)
at System.Xml.EncodingStreamWrapper..ctor(Stream stream, Encoding encoding)
at System.Xml.XmlUTF8TextReader.SetInput(Stream stream, Encoding encoding, XmlDictionaryReaderQuotas quotas, OnXmlDictionaryReaderClose onClose)
at System.Runtime.Serialization.XmlObjectSerializer.ReadObject(Stream stream)
at Sshfs.Utilities.Load[T](T obj, String file)
at Sshfs.MainForm.OnLoad(EventArgs e)
at System.Windows.Forms.Form.OnCreateControl()
at System.Windows.Forms.Control.CreateControl(Boolean fIgnoreVisible)
at System.Windows.Forms.Control.CreateControl()
at System.Windows.Forms.Control.WmShowWindow(Message& m)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.ScrollableControl.WndProc(Message& m)
at System.Windows.Forms.ContainerControl.WndProc(Message& m)
at System.Windows.Forms.Form.WmShowWindow(Message& m)
at System.Windows.Forms.Form.WndProc(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)

************** Loaded Assemblies **************
mscorlib
Assembly Version: 4.0.0.0
Win32 Version: 4.6.79.0 built by: NETFXREL2

CodeBase: file:///C:/Windows/Microsoft.NET/Framework/v4.0.30319/mscorlib.dll

WinSshFS
Assembly Version: 1.5.12.8
Win32 Version: 1.5.12.8

CodeBase: file:///C:/Users/Alexandru/Downloads/Release1.5.12.8/WinSshFS.exe

Microsoft.VisualBasic
Assembly Version: 10.0.0.0
Win32 Version: 14.6.79.0 built by: NETFXREL2

CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/Microsoft.VisualBasic/v4.0_10.0.0.0__b03f5f7f11d50a3a/Microsoft.VisualBasic.dll

System
Assembly Version: 4.0.0.0
Win32 Version: 4.6.79.0 built by: NETFXREL2

CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System/v4.0_4.0.0.0__b77a5c561934e089/System.dll

System.Windows.Forms
Assembly Version: 4.0.0.0
Win32 Version: 4.6.79.0 built by: NETFXREL2

CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Windows.Forms/v4.0_4.0.0.0__b77a5c561934e089/System.Windows.Forms.dll

System.Drawing
Assembly Version: 4.0.0.0
Win32 Version: 4.6.79.0 built by: NETFXREL2

CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Drawing/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll

Accessibility
Assembly Version: 4.0.0.0
Win32 Version: 4.6.79.0 built by: NETFXREL2

CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/Accessibility/v4.0_4.0.0.0__b03f5f7f11d50a3a/Accessibility.dll

System.Runtime.Remoting
Assembly Version: 4.0.0.0
Win32 Version: 4.6.79.0 built by: NETFXREL2

CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Runtime.Remoting/v4.0_4.0.0.0__b77a5c561934e089/System.Runtime.Remoting.dll

System.Configuration
Assembly Version: 4.0.0.0
Win32 Version: 4.6.79.0 built by: NETFXREL2

CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Configuration/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll

System.Core
Assembly Version: 4.0.0.0
Win32 Version: 4.6.79.0 built by: NETFXREL2

CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Core/v4.0_4.0.0.0__b77a5c561934e089/System.Core.dll

System.Xml
Assembly Version: 4.0.0.0
Win32 Version: 4.6.79.0 built by: NETFXREL2

CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Xml/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.dll

DokanNet
Assembly Version: 0.6.0.0
Win32 Version: 0.6.0.0

CodeBase: file:///C:/Users/Alexandru/Downloads/Release1.5.12.8/DokanNet.DLL

System.Runtime.Serialization
Assembly Version: 4.0.0.0
Win32 Version: 4.6.79.0 built by: NETFXREL2

CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Runtime.Serialization/v4.0_4.0.0.0__b77a5c561934e089/System.Runtime.Serialization.dll

SMDiagnostics
Assembly Version: 4.0.0.0
Win32 Version: 4.6.79.0 built by: NETFXREL2

CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/SMDiagnostics/v4.0_4.0.0.0__b77a5c561934e089/SMDiagnostics.dll

System.ServiceModel.Internals
Assembly Version: 4.0.0.0
Win32 Version: 4.6.79.0 built by: NETFXREL2

CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.ServiceModel.Internals/v4.0_4.0.0.0__31bf3856ad364e35/System.ServiceModel.Internals.dll

************** JIT Debugging **************
To enable just-in-time (JIT) debugging, the .config file for this
application or computer (machine.config) must have the
jitDebugging value set in the system.windows.forms section.
The application must also be compiled with debugging
enabled.

For example:

When JIT debugging is enabled, any unhandled exception
will be sent to the JIT debugger registered on the computer
rather than be handled by this dialog box.

Win-sshfs freeze trying to remount drive after Windows wake up from standby. Then, after killed and restarted the process, sometime drive information are erased forcing me to reinsert them.

Win-sshfs 1.5.12.8
Dokan 0.7.4.0
Windows 10 64bit

Hi,
unfortunately i have run into an issue:
Win-sshfs worked fine for some time but now every startup get the error massage "Bad drive letter"
With following details:
************** Exception Text **************
DokanNet.DokanException: Bad drive letter
at Sshfs.VirtualDrive.Mount()
at Sshfs.MainForm.OnLoad(EventArgs e)
at System.Windows.Forms.Form.OnCreateControl()
at System.Windows.Forms.Control.CreateControl(Boolean fIgnoreVisible)
at System.Windows.Forms.Control.CreateControl()
at System.Windows.Forms.Control.WmShowWindow(Message& m)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.ScrollableControl.WndProc(Message& m)
at System.Windows.Forms.ContainerControl.WndProc(Message& m)
at System.Windows.Forms.Form.WmShowWindow(Message& m)
at System.Windows.Forms.Form.WndProc(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)

************** Loaded Assemblies **************
mscorlib
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.34209 built by: FX452RTMGDR

CodeBase: file:///C:/Windows/Microsoft.NET/Framework/v4.0.30319/mscorlib.dll

WinSshFS
Assembly Version: 1.5.12.5
Win32 Version: 1.5.12.5

CodeBase: file:///C:/Users/Jonathan/Downloads/Release1.5.12.5/WinSshFS.exe

Microsoft.VisualBasic
Assembly Version: 10.0.0.0
Win32 Version: 12.0.20806.33440 built by: FX45W81RTMREL

CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/Microsoft.VisualBasic/v4.0_10.0.0.0__b03f5f7f11d50a3a/Microsoft.VisualBasic.dll

System
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.34239 built by: FX452RTMGDR

CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System/v4.0_4.0.0.0__b77a5c561934e089/System.dll

System.Core
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.34209 built by: FX452RTMGDR

CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Core/v4.0_4.0.0.0__b77a5c561934e089/System.Core.dll

System.Windows.Forms
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.34209 built by: FX452RTMGDR

CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Windows.Forms/v4.0_4.0.0.0__b77a5c561934e089/System.Windows.Forms.dll

System.Drawing
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.34209 built by: FX452RTMGDR

CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Drawing/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll

System.Runtime.Remoting
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.34243 built by: FX452RTMGDR

CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Runtime.Remoting/v4.0_4.0.0.0__b77a5c561934e089/System.Runtime.Remoting.dll

System.Configuration
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.34209 built by: FX452RTMGDR

CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Configuration/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll

System.Xml
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.34230 built by: FX452RTMGDR

CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Xml/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.dll

DokanNet
Assembly Version: 0.6.0.0
Win32 Version: 0.6.0.0

CodeBase: file:///C:/Users/Jonathan/Downloads/Release1.5.12.5/DokanNet.DLL

System.Runtime.Serialization
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.34230 built by: FX452RTMGDR

CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Runtime.Serialization/v4.0_4.0.0.0__b77a5c561934e089/System.Runtime.Serialization.dll

SMDiagnostics
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.34230 built by: FX452RTMGDR

CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/SMDiagnostics/v4.0_4.0.0.0__b77a5c561934e089/SMDiagnostics.dll

System.ServiceModel.Internals
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.34230 built by: FX452RTMGDR

CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.ServiceModel.Internals/v4.0_4.0.0.0__31bf3856ad364e35/System.ServiceModel.Internals.dll

This could have happened because added a usb drive (E:) while the share was still unmounted.
When i tried to mount, it probably had E: selected.
The GUI won't open. I changed inside config.xml in AppData the drive letter char value to 77 which would be M: but it still crashes.

Installed both Dokan 0.8 and various releases for win-sshfs but the gui for win-sshfs isn't opening at all. Right click menu for the task bar icon just freezes forcing me to close the program from task manager.

I planned to get rid of SMB on my Raspberry Pi, but for my backup scripts, I need to mount the sshfs drive only for the time of the backuping.

Will use "Mount on Login" with starting and killing the win-sshfs process with the script till then.
And yeah... I don't like this method. Especially I am connecting mostly to another server if I start win-sshfs, but it will automatically connect to my RPi. .

I have been trying to pull a Git repo I have on the a volume I mounted with win-sshfs, but it fails saying the repo dropped the connection which doesn't really make sense since Git sees it as a local drive. I found a link with the trouble though (https://www.eldos.com/forum/read.php?FID=21&TID=4269). Apparently to move a file on a SFTP server you need to first delete it then move it. Is there a way we can get a similar workaround in win-sshfs?

What happens:
Upon restarting win-sshfs after having set Virtual drive to OFF, the program shows the following message:

Virtual drive unable to connect: Bad drive letter

What was expected:
Upon restarting there would be no dialog box saying Virtual Drive Bad drive letter.

This is on Win10 64 bit.

HC

On latest debian stretch (OpenSSH 6.7) old key exchange mechanisms are disabled by default. The message when I click Mount is: No suitable authentication method found to complete authentication. And nothing is logged to auth.log on server, but the connection remains active. Putty has released an update recently to support more secure mechanisms, but it looks like RenciSSH library still doesn't support them.

http://www.openssh.com/txt/release-6.7

ssh -v server (debug) with default config expects these:
debug1: kex: server->client aes128-ctr [email protected] none
debug1: kex: client->server aes128-ctr [email protected] none
debug1: sending SSH2_MSG_KEX_ECDH_INIT
debug1: expecting SSH2_MSG_KEX_ECDH_REPLY

I can't tell for sure if this is the problem, but the connection is never successful with any password and even when using public key. Let me know if I can test something for you.

When I tried to compile it, VS occured an error, "Can't import sshfs_4every1.pfx."
Also, password of signature is needed to import.

So.. I think that to distribute complied version together is better idea.

Thanks

HI,

When opening some files directly from the SSHFS mount such as xls (but not xlsx) or SolidWorks files, the file could be opened as readonly or it will fail.

I do not have much more idea at the moment about what could cause this issue.

Thanks

From a local mount, if you try to delete a file on the remote system, the file immediately disappears from the local mount, and it appears to delete OK; however, when there are remote permission issues with the actual deletion, the user doesn't know, and the files simply reappear when you refresh the view.

It seems like the file deletes are not confirmed remotely before updating the local file listing. Perhaps a better approach would be to validate the delete occurs remotely and then handle local update to file listing (remove if successful, or display user error w/permission denied as replied by remote SSH server).

Greetings, please add the ability and option dialog check-box for optionally using the None cipher.

This is a post-authentication cipher for use inside an otherwise protected or trusted network, eg. inside VPN (already encrypted), office cable LAN, etc. and obviously provides huge performance gains for such situations.

Example code and documentation reference for this "None switch" is available at the website of the Pittsburg Supercomputing Center's website for the High Performance Networking (HPN) SSH patchset.

For reference, the HPN patchset is becoming more and more widespread use, and packages are available in Debian and Ubuntu standard repositories, so it is not something "exotic". The patchset is also backward-compatible; it is the same SSH protocol, the same OpenSSH server software, but optimized buffer handling and windowing, which provides big performance gains, so it is a no-brainer to install it, so I can only assume that its deployment is on the rise.

Besides the other mentioned SSH optimizations from the patchset, the None cipher provides considerable performance boost when network protection / confidentiality on the network is already otherwise protected or not necessary.

It is only one additional cipher without any actual encryption being at work, so implementation effort should be relatively small.

I am not sure, if this issue is to be filed here or at the Dokany library, but I wanted to voice this feature enhancement proposal for the None cipher on some place, to get started.

The tab order of the input field is mapped incorrectly. Not a huge deal but it's still a bit of an annoyance.

Hi,
I'm experiencing the above mentioned error and I'm not entirely sure if it's a bug or if I'm using the program incorrectly. Could you please help? Included screenshot has the full popup as it appears on my machine running Windows 8.1

On Windows 10, using either v0.7.2 or v0.7.3-RC4 (latest) from https://github.com/dokan-dev/dokany/releases I get the following error:

When I mount a drive, disconnect cable for a while, and reconnect it back, the remote drives remain to seem empty until I remount them.

At best, there should be automatic reconnect ability.

Hi,

In my environment: Windows 8.1, sshd server in Android 4.4: I have this error. I know the password is correct because I can do ssh with Putty. I tried private key, same issue. When I type a wrong password, I have permission denied so it is an issue after password authentication. This occur with latest 1.5.12.8 and 1.5.12.7 , and Dokany 0.7.4.

i can create new file and edit old ones, but i cannot delete them

i'm using latest version of winsshfs and dokan

version 1.5.12.5 works

thanks in advance

Dokany breaks user-space compatibility from 0.8.0 and up. Which version should be used with win-sshfs 1.5.12.9 rc1, 1.5.12.8 releases?

Is it possible to create the local windows drive as a network drive instead of a removable disk?

The problem is that whenever my virus scanner runs, it hammers my SSH server because it thinks the SSH drive is a local jump drive or something so it wants to scan all the files. Most virus scanners doesn't scan network disks in my experience, so it would be nice to either always create them as network drives, or have the option to choose removable or network disk in configuration.

Looks like i can select network drive of already attached drive, if its is not currently available (offline). Others are not in list. More on screenshot.

• able "mount" it - wont do anything and after "unmount" button stays gray and application has to be killed with task manager to shut it

(c) mspaint skills 2015

Setting the virtual drive to off, saving, restarting win-sshfs gives "Bad drive letter" on startup. Can you please look into this minor issue? I'm using win-sshfs 1.5.12.8 with Dokan 8 and Windows 10. Thank you!

Hello, please add the ability to connect to an existing server without saving password, example for sensitive server accounts so that no password is stored on client machine.

Current progression:

1. Open connect dialog.
2. Select a desired server from list. Password form field is empty.
3. Enter password.
4. Click button "Mount".
5. Message box appears: "Permission denied (password)".

Workaround:
6. Enter password.
7. Click button "Save".
8. Click button "Mount".
9. Drive connects as desired.
10. Clear form field for password.
11. Click button "Save".

It seems only when one clicks save password, then it has the password. It seems the connect methods access values from appdata and not the form field. At least for the password, it would be desirable to read the value from the connect dialog form field (override data in config file).

Desired progression:
5. Drive connects as desired.
6. Password field is automatically cleared by program.

does not support openssh keys? what do I use?

Sshfs Manager - 4every1 edition - v. 1.5.12.8
xx could not connect:
Key 'OPENSSH' is not supported.

Version 1.5.12.9 rc1 used to work for a moment. Now it gives an error "Server string is null or empty." Which string does this refer to?

First thank you for trying to keep this great project alive.
I have some interrogation about the dependency management. I can see you added DokanNet and SSH.NET source code on the repo, and even committed changes (bug fix and feature). This doesn't look clean and you now have to manage three projects as one.

As you may have noticed, after providing DokanY I'm now trying to reunificate the Dokan community and main associated projects.
DokanNet repository that I will maintain is located here: https://github.com/dokan-dev/dokan-dotnet and I also push releases to NuGet here: https://www.nuget.org/packages/DokanNet/
If you could pull request your DokanNet changes on it, I will be happy to review/discuss them and then update the repository and continue its support.

About SSH.NET, I saw you patched it for Pageant support and that's a great addition. But couldn't you do it using the official release? I though from what I read that it could have been the case. Wasn't it possible to create a new SSH.NET Pageant Module project on another repository which depends of SSH.NET (NuGet reference again), create associated NuGet package for it and add both dependencies to Win-SSHFS?

Also, it seems you committed files specific to your environment (bat, ...). Even the versioning convention is weird, you talk about SVN but here you are using Git.

Thanks!

The drive letter Z seems to be available only for the virtual spool drive. It would be great to have it available for regular drives if the user wants to use Z: for regular drive.

After editing a drive you are unable to unmount the drive.

Version 1.5.12.8 zip file on Win7 Pro 64bit Intel.

What happens:
After mount - unmount - it is no longer possible to mount. After clicking the Mount button it stays grey and no mount appears for the server.

What was expected:
After mount - unmount - it should be possible to mount again.

Additional:
After killing WinSshFS.exe and restarting it, you can mount again.

Mount - unmount - mount failure seems to also apply to the spool drive.

After the mount - unmount mount (now grey button), if you try to delete the server/drive entry, the app hangs and it is no longer possible to move the Manager window .

HC

I suggest using the dokanx library instead of the dokan library since dokanx is still being updated while dokan isn't.

The drive symbol did appear in 'This PC' but the drive size was not shown.

After a few seconds, windows died with following message

BAD_POOL_CALLER

I'm using windows 10 on surface pro 3.

When changing machine name and rebooting, one gets an exception telling that an exception ocurred during deserialization.

Removing the WinSSHFS folder in AppData solves the problem.

Thanks

When I try to copy/paste files to a mounted drive it gives me a permission denied error. However, I am able to create new files etc.

I am trying to use win-sshfs releases, 1.5.12.9 rc1 or 1.5.12.8 with Donaky 0.7.4 with Windows 8.1 x64 Pro. When i try to start win-sshfs I receive the following unhanded exception:

System.Runtime.Serialization.SerializationException: There was an error deserializing the object of type System.Collections.Generic.IEnumerable`1[[Sshfs.VirtualDrive, WinSshFS, Version=1.5.12.8, Culture=neutral, PublicKeyToken=d3cb22b275540e19]]. The data at the root level is invalid. Line 1, position 1. ---> System.Xml.XmlException: The data at the root level is invalid. Line 1, position 1.
at System.Xml.XmlExceptionHelper.ThrowXmlException(XmlDictionaryReader reader, String res, String arg1, String arg2, String arg3)
at System.Xml.XmlUTF8TextReader.Read()
at System.Xml.XmlBaseReader.IsStartElement()
at System.Xml.XmlBaseReader.IsStartElement(XmlDictionaryString localName, XmlDictionaryString namespaceUri)
at System.Runtime.Serialization.XmlReaderDelegator.IsStartElement(XmlDictionaryString localname, XmlDictionaryString ns)
at System.Runtime.Serialization.XmlObjectSerializer.IsRootElement(XmlReaderDelegator reader, DataContract contract, XmlDictionaryString name, XmlDictionaryString ns)
at System.Runtime.Serialization.DataContractSerializer.InternalIsStartObject(XmlReaderDelegator reader)
at System.Runtime.Serialization.DataContractSerializer.InternalReadObject(XmlReaderDelegator xmlReader, Boolean verifyObjectName, DataContractResolver dataContractResolver)
at System.Runtime.Serialization.XmlObjectSerializer.ReadObjectHandleExceptions(XmlReaderDelegator reader, Boolean verifyObjectName, DataContractResolver dataContractResolver)
--- End of inner exception stack trace ---
at System.Runtime.Serialization.XmlObjectSerializer.ReadObjectHandleExceptions(XmlReaderDelegator reader, Boolean verifyObjectName, DataContractResolver dataContractResolver)
at System.Runtime.Serialization.XmlObjectSerializer.ReadObject(XmlDictionaryReader reader)
at System.Runtime.Serialization.XmlObjectSerializer.ReadObject(Stream stream)
at Sshfs.Utilities.Load[T](T obj, String file)
at Sshfs.MainForm.OnLoad(EventArgs e)
at System.Windows.Forms.Form.OnCreateControl()
at System.Windows.Forms.Control.CreateControl(Boolean fIgnoreVisible)
at System.Windows.Forms.Control.CreateControl()
at System.Windows.Forms.Control.WmShowWindow(Message& m)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.ScrollableControl.WndProc(Message& m)
at System.Windows.Forms.ContainerControl.WndProc(Message& m)
at System.Windows.Forms.Form.WmShowWindow(Message& m)
at System.Windows.Forms.Form.WndProc(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)

I am unable to start the latest win-sshfs due to this error.

Where can I tell win-sshfs which drive letter to use? Is there another fix for this?

Using Dokan 0.7.4 and have tried win-sshfs release 1.5.12.8 as well as 1.5.12.9-rc1. I am experiencing very poor file copy performance from a mounted sshfs to local disk (max of ~550 kB/s). I have a very high-speed internet connection and no problem with speeds using SFTP standalone (usually get ~10 MB/s). Is this a limitation of the SSH.Net library used here?