Public keys authorized lost after restart

[jamesfawcett]

Hello,

My NS1 is still working great thank you! I have one issue though.

I use ssh-copy-id to save my public key on the NAS. After reboot, this key is lost.

I checked in the interface and it disappears there too.

Is there any way to make them persist?

Thanks
James

[Jocko]

Hi

Thank you for your feedback.

I use ssh-copy-id to save my public key on the NAS. After reboot, this key is lost.

I checked in the interface and it disappears there too.

can you give more detail.

Usually you just have to paste your public key from the ssh menu in the related textbox

[jamesfawcett]

When I use ssh-copy-id to the NAS, I can see them listed here (screenshot). I don't see an option to add the keys in the FVDWSL-BASE.

Should I be generating the keys on the NAS instead, and using that key on the client?

Thanks
James

[Jocko]

So I understood...

You did not select the option "SSH Access with rsa key" and when you use ssh-copy-id (which is not included in our firmware) it creates some files which allows to use this mode at the same time with the mode "SSH Access by pwd". So when you reboot the nas, the firmware removes these files.

We want to keep the following behaviour with our firmware : do not to allow both modes at the same time... It is our choice because usually the key mode is often used to get a WAN remote access and then you must open the ssh port. This port is systematically sniffed by some malicious bots and you can got some database on the net according with the researched machine profile. I post here an example with the apache server: http://www.base64online.com/hc.php?q=fvdw-sl%20NAS%20Management. So with these two hosts (old recording,I know it is a machine using our firmware and I can also try to connect to the ssh server !!! As the default login is known (and I found a site which lists it!) I will get a root access if the user does not have yet changed the password !

And think at each time you upgrade the firmware the custom password of the root account is also reset...

So in your case, do not use ssh-copy-id and you just have to change the login mode and paste your public key. (Please to read the help page)

[jamesfawcett]

Great ok thank you Jocko, and makes good sense for security :) Thanks for your help. I will find another way without using ssh-copy-id.

ps - the ssh-copy-id is set on my raspberry pi. The Raspberry Pi rsync's all the files to the NAS to /share/1000/Backups/ every week. It works very well, very stable :)

Thanks
James