TOS 6.0.535 (X86) is Released for Update

[mrslother]

Since you have switched to TOS6 system, the previous authorized_keys file may not be applicable. You can try to regenerate a new authorized_keys file.

I recreate the file with no luck. Regenerating an SSH authorized_keys file historically has been simply appending the output of your public keys:

Code: Select all

cat id_rsa.pub >> authorized_keys

Or is there something special about TOS that requires a different approach?

[TMlinda]

You can use the following command to generate a key on the client and import it into the TNAS system.

Code: Select all

ssh-keygen

Code: Select all

ssh-copy-id -p 9222 [email protected]

[mrslother]

Thanks, TMwuu. But...
a) I already have ssh keys I use across my other systems. I prefer to not regen keys for each box; SSH does not require doing so.
b) ssh-copy-id does not exist on Windows. All it does is ssh into your home dir and append the contents of your default pub key to the authorized_keys file. I can do that manually.

So, the bigger question is why this is not working? It works, with this pub key, on a variety of other linux boxes as well as the TOS5 system I had on this unit before updating to TOS6.

[Lex]

Problem with SSH and authorized_keys.

Just received u4-423; tried TOS5, updated authorized_keys file with my pub keys. SSH'ing worked great using keys.

Decided to try TOS6 so I factory reset then manually installed TOS6 then updated to latest: 6.535.00158.
For the love of God, I cannot get authorized_keys to work. I can ssh in with password, but no matter what I do with the same authorized_keys file I previously used, it always requires the password.

I've tried various options found in this forum, but nothing worked.

Please help!

Check permission for .ssh folder and files. Only owner mast have access.

[mrslother]

Check permission for .ssh folder and files. Only owner mast have access.

Thank you for chiming in. Verified that only the account owner has access:

Code: Select all

myusername@NAS:~# ls -la
total 4
drwxrwxrwx+ 1 myusername myusername   112 Nov 29 14:36 .
drwxrwxrwx+ 1 myusername myusername    32 Nov 29 15:25 ..
-rw-------+ 1 myusername myusername  2365 Nov 30 12:07 .bash_history
drwx------+ 1 myusername myusername    30 Nov 29 14:36 .ssh

myusername@NAS:~# cd .ssh
myusername@NAS:~/.ssh# ls -la
total 4
drwx------+ 1 myusername myusername  30 Nov 29 14:36 .
drwxrwxrwx+ 1 myusername myusername 112 Nov 29 14:36 ..
-rw-------+ 1 myusername myusername 762 Nov 29 14:36 authorized_keys

[Mamex]

Hi everyone I'm a new user and I'm waiting for an F4-424 I hope to be well and to be able to update it easily to the new release

[Lex]

try on NAS

Code: Select all

tail -f  /var/log/auth.log 

and login over ssh.

[Mamex]

I switched from .145 to .530 and now it correctly notified me of the .535 downloading. I have not encountered any problems even though it has been in use for less than 5 hours

[mrslother]

try on NAS

Code: Select all

tail -f  /var/log/auth.log 

and login over ssh.

Lex, you are my hero! The error shown in the auth.log directed me to the right path. As you said above, only the user can have access to the .ssh directory. That was true for my .ssh dir, but not my ~ dir. Fixed. I'm working again.

Thank you!

[desallesp]

Is there any update on UPS issue where it only works for 30mins to 1 hour then the checkbox for Enable UPS Support becomes unticked and if you try to enable UPS support it can't detect the UPS until the NAS is rebooted ?

Did you get any news on this? I have the same occurring to me on a new F4 424 Pro