[solved] sshfs not working for me

[Lee]

Can't get sshfs to work.  Less than a week ago I thought, "wouldn't it be great to have sshfs?".  And there it is.  But I can't get it ti work.  Probably just something dumb that I'm missing.  It asks for the password, I provide the password and it disconnects,  Ssh works fine with the same password, of course, as shown below.

I've tried various combinations of full paths for both the remote directory and the mountpoint and have tried the whole mess with sudo as well.  (The mount point is /home/tc/asimov.) The remote computer (its only 5 feet away) is running tc 1.3, the local is running tc 1.2.

Code: [Select]

tc@oklahoma:~$
tc@oklahoma:~$
tc@oklahoma:~$ sshfs tc@192.168.0.27: asimov
tc@192.168.0.27's password:
remote host has disconnected
tc@oklahoma:~$
tc@oklahoma:~$
tc@oklahoma:~$ ssh tc@192.168.0.27

Secure login powered by Dropbear SSH server.
tc@192.168.0.27's password:
 (o-
 //\  Tiny Core Linux 1.3
 v_/_       asimov

tc@asimov:~$ exit
Connection to 192.168.0.27 closed.
tc@oklahoma:~$
tc@oklahoma:~$


[alu]

isn't sshfs used in order to mount drive on a remote machine? if yes, i think it is more somthg like:

sshfs tc@ip-of-the-remote-host:/disk-or-folder-to-mount /place-where-to-mount-it-on-your-machine (typically /home/tc/folder-or-mount-point)

the remote host will then ask for the password, and should let you log in.

(it might be smthg slightly different since i dont use ssh for a while)

[Lee]

isn't sshfs used in order to mount drive on a remote machine? if yes, i think it is more somthg like:

sshfs tc@ip-of-the-remote-host:/disk-or-folder-to-mount /place-where-to-mount-it-on-your-machine (typically /home/tc/folder-or-mount-point)

Yes that's it exactly.  If I understand it correctly, the default directory to mount will be the specified user's home directory (if nothing is given following the colon), and if the mount point is in the current directory there should be no need to specify its full path.  In any case specifying full paths:

Code: [Select]

tc@oklahoma:~$
tc@oklahoma:~$ sshfs tc@192.168.0.27:/home/tc /home/tc/asimov
tc@192.168.0.27's password:
remote host has disconnected
tc@oklahoma:~$

yields the same result.

[combo3]

Unfortunately, Dropbear doesn't support sftp out of the box.

You have two options:

1) install and run openssh on the host, or

2) download openssh and extract the missing binary:

   - Open appbrowser
   - Select Connect > TCZ > openssh.tcz
   - Click on Download Only
   - Select File > Install Optional > openssl-0.9.8h.tczl
   - Click: Ok
   - Select: File > Install Optional > openssh.tcz (but don't install it)
   - Make note of the path in the textbox next to Filename:
   
   - Open Aterm

Code: [Select]

$ mkdir openssh
$ sudo mount -o loop /path/to/tce/optional/openssh.tcz openssh
$ sudo mkdir /usr/libexec
$ sudo cp openssh/usr/local/libexec/sftp-server /usr/libexec
$ sudo umount openssh
$ rmdir openssh   
   - Open control panel and start SSH server

To make it permanent, add /usr/libexec/sftp-server to /opt/.filetool.lst
and keep openssl-0.9.8h.tczl in your tce directory.

[Lee]

Unfortunately, Dropbear doesn't support sftp out of the box.

You have two options:

1) install and run openssh on the host, or

2) download openssh and extract the missing binary:

Thanks for the detailed info.  I'll try that this evening.

I had thought that I was all set since scp works, but sshfs running over sftp explains the problem.

[Lee]

Thank you combo3.   That worked very nicely.

I ended up turning off dropbear (at the control panel "SSH Server" button) and installing the full extension of openssh.tcz.  Then I started sshd from the command line.

I eventually cleared out ~/.sshd/known_hosts completely on both boxes before I got sshfs to work.  I don't know if it was necessary to do that on both, but whichever one I did first didn't do the trick.

[Juanito]

I played around with this a while, but couldn't make it work.

I guess the trick is in "Then I started sshd from the command line" - I presume various keys need to be generated (in a similar fashion to /etc/init.d/dropbear), but which keys and where?

..and which extensions are required on the server and which extensions are required on the client.

I tried the short cut, by copying /usr/local/libexec/sftp-server from the openssh extension, but this didn't want to work with the base tc ssh server either.

[combo3]

Actually, the copy/paste process is no longer necessary.

Server Setup

1) Download and install the extension sftp-server submitted by Daniel Barnes

ftp://distro.ibiblio.org/pub/linux/distributions/tinycorelinux/tcz/
ftp://distro.ibiblio.org/pub/linux/distributions/tinycorelinux/tce/

(Note: although these files are located in the TC 1.x respository they work just as well with TC 2.2)

2) Create a password for user tc:

Code: [Select]

sudo passwd tc
3) Start Dropbear via  Contol Panel > SSH Server

Done!


Client Setup

Install extension sshfs-fuse-2.2 with appbrowser

Done!

Now Try It Out!

On the SSH server:

1) Open a terminal and create a test directory in /home/tc

Code: [Select]

mkdir beatles
2) Switch to your directory and create some empty files

Code: [Select]

cd beatles
touch john paul george ringo
3) Get your ip address

Code: [Select]

ifconfig eth0 | grep inet

On the client

4) Open a terminal and create a mountpoint in /home/tc

Code: [Select]

mkdir ssh-host
5) Invoke the sshfs command

Code: [Select]

sshfs -d tc@ip_addresss_from_step_3:/home/tc/beatles ssh-host
6) You should see something similar to this:

Host 'x.x.x.x' is not in the trusted hosts file.
(fingerprint md5 fb:e0:52:98:fe:ab:ef:f9:f0:4a:78:8e:2f:5c:36:c0)
Do you want to continue connecting? (y/n)

(Note: if you leave out the -d switch, the cursor will hang and wait for confirmation without displaying the message.)

7) Press y and hit enter

Supply your password

9) Issue a list command on the mounted directory

Code: [Select]

ls ssh-host
You should see the files created in step 2.

To Unmount

From the /home/tc directory on the client enter:

Code: [Select]

fusermount -u ssh-host
{Edit: Added unmount instructions}

[combo3]

On a side note, I just noticed an error in my submission.

The openssh and openssl-0.9.8h dependencies are not required by sshfs-fuse-2.2 on the client.
 
Could whoever administers the extensions please remove them from the dependency list and info file.

Thanks.

[curaga]

On a side note, I just noticed an error in my submission.

The openssh and openssl-0.9.8h dependencies are not required by sshfs-fuse-2.2 on the client.
 
Could whoever administers the extensions please remove them from the dependency list and info file.

Thanks.

Done.

[tinypoodle]

On a side note, I just noticed an error in my submission.

The openssh and openssl-0.9.8h dependencies are not required by sshfs-fuse-2.2 on the client.
 
Could whoever administers the extensions please remove them from the dependency list and info file.

Thanks.

Done.

At current those deps are present, as well in 2.x as in 3.x repos.
And I recall having given up on sshfs-fuse a few months ago already, exactly to avoid those deps, when I preferably use dropbear over openssh.

[danielibarnes]

Actually, the copy/paste process is no longer necessary.

Server Setup

1) Download and install the extension sftp-server submitted by Daniel Barnes

ftp://distro.ibiblio.org/pub/linux/distributions/tinycorelinux/tcz/
ftp://distro.ibiblio.org/pub/linux/distributions/tinycorelinux/tce/

(Note: although these files are located in the TC 1.x respository they work just as well with TC 2.2)

I should probably update that ...

[combo3]

On a side note, I just noticed an error in my submission.

The openssh and openssl-0.9.8h dependencies are not required by sshfs-fuse-2.2 on the client.
 
Could whoever administers the extensions please remove them from the dependency list and info file.

Thanks.

Done.

At current those deps are present, as well in 2.x as in 3.x repos.
And I recall having given up on sshfs-fuse a few months ago already, exactly to avoid those deps, when I preferably use dropbear over openssh.

The openssh deps were removed, but I reinstated them in an updated submission after further testing revealed that while dropbear and sshfs-fuse worked well on the same network, connections to outside hosts would hang and timeout.

I've just tested them together again... without success. If you plan on using dropbear/sshfs-fuse only on a local network, then a possible workaround would be to manually remove openssh from the sshfs-fuse dep file.

However, I'm open to other suggestions.

[tinypoodle]

Ah, makes sense then, thanks

[tinypoodle]

Actually, the copy/paste process is no longer necessary.

Server Setup

1) Download and install the extension sftp-server submitted by Daniel Barnes

ftp://distro.ibiblio.org/pub/linux/distributions/tinycorelinux/tcz/
ftp://distro.ibiblio.org/pub/linux/distributions/tinycorelinux/tce/

(Note: although these files are located in the TC 1.x respository they work just as well with TC 2.2)

I should probably update that ...

Sounds like a plan  

Code: [Select]

tc@box:~$ tce-load -i /tmp/tce/optional/sftp-server.tcz
mount: mounting /dev/loop4 on /tmp/tcloop/sftp-server failed: Invalid argument
/tmp/tce/optional/sftp-server.tcz: OK
Took me a while to find out that this extension is in a format other than squashfs...