plugout.net

Hi! When I had my old Lacie-firmware I was able to get ssh acces with my browser, using Thunar on linux-Mint (ssh://root@myserver).
Now after upgrading to fvdwsl-15-3 It gives the error that it can't open filesystem.
Although I can use ssh over the terminal, that is working fine. So I did re-generate the rsa-key.
But it would be much more practical if I can use te browser again.
Someone any idea why ssh gets blocked for the file-browser?

Oké I solved it. Turnes out in /home/user/.ssh/ folder is also an 'known_hosts' file that needed to be adjust.

Gromke wrote:Oké I solved it. Turnes out in /home/user/.ssh/ folder is also an 'known_hosts' file that needed to be adjust.

:scratch there is no such directory in our firmware

That's right, I had to edit this file in my own filesystem. It had still the old rsa-key in it and that was conflicting.
there is also an known_hosts file in /root/.ssh/ (local linux system) and these files apparently need to contain the rsa-key shown in the ssh setting from the web-interface.
I just missed the one in the /home/user/.ssh/ folder.

we store the the .ssh folder on a different place follow the link in system root.
That one is used by dropbear the ssh server we use.
Did you install another ssh server ?

fvdw wrote:Did you install another ssh server ?

No, just the included ssh server.
To be more specific, I had to change these files on my computer, running Linux Mint, not in the nas.
So this topic can be marked as solved

Gromke wrote:Hi! When I had my old Lacie-firmware I was able to get ssh acces with my browser, using Thunar on linux-Mint (ssh://root@myserver).
Now after upgrading to fvdwsl-15-3 It gives the error that it can't open filesystem.

Hi Gromke,

When you install the fvdw-sl firmware, a new private key is generated. And of course, you must update all known_hosts file on each client

Note: the firmware uses dropbear as ssh server: it has the same main features than openSSH. The ssh client command is not ssh but dbclient.

The ssh client command is not ssh but dbclient

Thanks! this is new to me. I was using ssh from my linux, talking to the nas, that is working fine to.
The known-hosts stuff I figured out and is all done.
So talking back I could use the dbclient command in combination with rsync? (that indeed didn't work with ssh...)
Well, I just try.... Thanks

So talking back I could use the dbclient command in combination with rsync? (that indeed didn't work with ssh...)
Well, I just try.... Thanks

Yes, Gromke.

Currently, to make backup, the firmware uses rsync with or not over a ssh channel.

In the help pages, you can find information and also on the board some howtodo written by uelpenich.