that looks good, so it must be something else. The .ssh directory itself has to be drwx------ (ls -ld /root/.ssh, or wherever your root's .ssh is)
BTW the 'remote' system is the localhost, which you're ssh-ing to. So look at the sshd daemon messages on your local system. if your system uses systemd, you may need to use journalct I think and/or run sshd with verbose error logging. Sorry for being vague, I don't remember the details and I can' check them right now. On Thu, Oct 24, 2019 at 12:20 PM Rich Shepard <[email protected]> wrote: > On Thu, 24 Oct 2019, Przemek Klosowski wrote: > > > I didn't follow the entire thread, but seeing that it sees your keys but > > refuses to use them, sometimes that is caused by sshd being picky about > the > > permissions on the key file. > > Przemek, > > # ll .ssh/ > total 20 > -rw------- 1 root root 92 Oct 24 07:41 authorized_keys > -rw-r--r-- 1 root root 249 Nov 15 2018 config > -rw------- 1 root root 399 Oct 23 11:39 id_ed25519 > -rw-r--r-- 1 root root 92 Oct 23 11:39 id_ed25519.pub > -rw------- 1 root root 326 Oct 23 15:46 known_hosts > > > you have to look at sshd log files on the remote connection. > > The 'remote connection' is an external USB hard drive. No OS, no users, > just > like a USB flash drive. It's for backup data only. > > Regards, > > Rich > _______________________________________________ > Dirvish mailing list > [email protected] > http://www.dirvish.org/mailman/listinfo/dirvish >
_______________________________________________ Dirvish mailing list [email protected] http://www.dirvish.org/mailman/listinfo/dirvish
