[Dirvish] Setting up new backup

[Paul Slootman]

BTW, did you try already removing the root@ from the client: line?


On Thu 24 Oct 2019, Rich Shepard wrote:
> 
> I happened to be in root/s .ssh/ directory when I ran the command.

OK

> > First with, and the without the path?
> 
> With the absolute path:
> # ssh -vi /root/.ssh/id_ed25519 localhost 
> OpenSSH_7.4p1, OpenSSL 1.0.2t  10 Sep 2019
> debug1: Reading configuration data /root/.ssh/config
> debug1: Reading configuration data /etc/ssh/ssh_config
> debug1: Connecting to localhost [127.0.0.1] port <redacted>.
> debug1: Connection established.
> debug1: permanently_set_uid: 0/0
> debug1: identity file id_ed25519 type 4
> debug1: key_load_public: No such file or directory
> debug1: identity file id_ed25519-cert type -1

Note that the "key_load_public: No such file or directory" message is
about the file mentioned in the line below the message, i.e. in this
case id_ed25519-cert; which is not a problem.

> debug1: identity file /root/.ssh/id_ed25519 type 4

This one is loaded OK

> debug1: key_load_public: No such file or directory
> debug1: identity file /root/.ssh/id_ed25519-cert type -1

id_ed25519-cert is again not loaded (as it doesn't exist).

> debug1: Next authentication method: publickey
> debug1: Offering ED25519 public key: id_ed25519
> debug1: Authentications that can continue: publickey
> debug1: Offering ED25519 public key: /root/.ssh/id_ed25519
> debug1: Authentications that can continue: publickey
> debug1: No more authentication methods to try.

Somehow the server rejects the id_ed25519 public key.

> The past two days in /var/log/secure:

no sshd messages.

I see that in my system (Debian) sshd messages are logged in
/var/log/auth.log .

> > I note you didn't check (or at least didn't show) the permissions of the
> > directories /root and /root/.ssh
> 
> # ll /
> total 120
> drwxr-xr-x   2 root root  4096 Jul 16 13:09 bin/
> drwxr-xr-x   5 root root  4096 Aug 28 07:16 boot/
> drwxrwxrwx  26 root root  4096 Oct  4 16:04 data/
> drwxr-xr-x  16 root root  5580 Oct 23 15:26 dev/
> drwxr-xr-x 111 root root 12288 Oct 23 16:51 etc/
> drwxr-xr-x   2 root root  4096 Sep 23  2018 flashdr/
> drwxr-xr-x   5 root root  4096 Nov 11  2018 home/
> drwxr-xr-x   7 root root  4096 Sep  8 08:12 lib/
> drwxr-xr-x   2 root root 12288 Sep 17 07:18 lib64/
> drwx------   2 root root 16384 Dec 31  2007 lost+found/
> drwxr-xr-x  16 root root  4096 Dec 31  2007 media/
> drwxr-xr-x  13 root root  4096 Oct 19 13:41 mnt/
> drwxrwxrwx  49 root root  4096 Oct 10 13:50 opt/
> dr-xr-xr-x 341 root root     0 Oct 21 22:57 proc/
> drwx--x---  26 root root  4096 Oct 23 16:16 root/

The extra x is a bit strange, but should be OK.
It's easier to show directory permission with
ls -ld dir1 dir2

> # ll /root/.ssh/

This only shows the contents of the .ssh directory, not the directory
itself.

> total 20
> -rw------- 1 root root  93 Oct 23 15:09 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

Hmm, why is the authorized_keys file 1 byte larger than id_ed25519.pub?
Try just copying id_ed25519.pub to authorized_keys


Paul