Tag Info

New answers tagged

0

I'm not sure the output of sshfs is caugh in expect. This may be your problem - the script terminates without sending the password, which would cause the problem you describe. Another possible scenario is that sshfs is actually sending you the output user@domain password:, and expect may not like it. However, this really isn't a good way of dealing with ...


1

FUSE doesn't have any generic support for the remount option. In 2006 with FUSE 2.6 this was described as impossible to do for a FUSE-based filesystem without patching FUSE itself (fuse-devel thread “Remounting in FUSE support”). There doesn't seem to have been any progress since then. There are requests for remount support in SSHFS (e.g. Ubuntu bug ...


0

Too late to answer but I think these two points are very important Check the permission of your home directory in the server as well. I faced a similar problem and the problem was home directory permission. So two things Your authorized_keys should be 600 Your home directory should be 755 sshd by default logs some messages into /var/log/secure at least ...


0

This might be an easier way to do it, but I can't speak on the security of this method: Create a file at /home/user/sshfs with your password in it. Edit /etc/rc.local and before the exit 0 add the following code: sshfs user@ipor.com:/Remote/Path/To/Mount /local/path/to/mount -o workaround=rename -o gid=xx,uid=xxxx -o allow_other -o password_stdin < ...


1

THe SSHFS filesystem is built on top of the SFTP protocol. SFTP provides only facilities to manipulate files in “classical” ways; the client makes a request to the server (list a directory, upload a file, etc.), and the server responds. There is no facility in this protocol for the server to spontaneously notify the client that something has happened. This ...



Top 50 recent answers are included