On Thu, 24 Oct 2019, Eric V. Smith wrote: > I’m not sure my phone is quoting this entire message. Apologies if this is > messed up.
Eric, Phone must be too small for the message. :-) > I find that “ssh -vv” (two v’s) is helpful for debugging permission > problems. Here it makes no difference over the output of a single 'v.' The debug2 rows concern ciphers. Selected rows from the output: debug1: identity file /root/.ssh/id_ed25519 type 4 debug1: Host '[localhost]:<redacted>' is known and matches the ED25519 host key. debug1: Found key in /root/.ssh/known_hosts:3 debug2: set_newkeys: mode 1 debug1: rekey after 134217728 blocks debug1: SSH2_MSG_NEWKEYS sent debug1: expecting SSH2_MSG_NEWKEYS debug1: SSH2_MSG_NEWKEYS received debug2: set_newkeys: mode 0 debug2: service_accept: ssh-userauth debug1: SSH2_MSG_SERVICE_ACCEPT received debug1: Authentications that can continue: publickey debug1: Next authentication method: publickey debug1: Offering ED25519 public key: /root/.ssh/id_ed25519 debug2: we sent a publickey packet, wait for reply debug1: Authentications that can continue: publickey debug1: Offering ED25519 public key: /root/.ssh/id_ed25519 debug2: we sent a publickey packet, wait for reply debug1: Authentications that can continue: publickey debug2: we did not send a packet, disable method debug1: No more authentication methods to try. Permission denied (publickey). Sigh, Rich _______________________________________________ Dirvish mailing list Dirvish@dirvish.org http://www.dirvish.org/mailman/listinfo/dirvish
