On 02/24/2017 10:50 AM, Rich Shepard wrote: > On Fri, 24 Feb 2017, Rich Shepard wrote: > >> debug1: Connecting to salmo [192.168.55.1] port <>. >> debug1: Connection established. > > The two hosts can communicate. > >> debug1: key_load_public: No such file or directory >> debug1: identity file /home/rshepard/.ssh/id_rsa type -1 >> debug1: key_load_public: No such file or directory >> debug1: identity file /home/rshepard/.ssh/id_rsa-cert type -1 >> debug1: key_load_public: No such file or directory >> debug1: identity file /home/rshepard/.ssh/id_dsa type -1 >> debug1: key_load_public: No such file or directory >> debug1: identity file /home/rshepard/.ssh/id_dsa-cert type -1 >> debug1: key_load_public: No such file or directory >> debug1: identity file /home/rshepard/.ssh/id_ecdsa type -1 >> debug1: key_load_public: No such file or directory >> debug1: identity file /home/rshepard/.ssh/id_ecdsa-cert type -1 >> debug1: key_load_public: No such file or directory >> debug1: identity file /home/rshepard/.ssh/id_ed25519 type -1 >> debug1: key_load_public: No such file or directory > > Not finding the public key. > >> debug1: Host '[salmo]:21498' is known and matches the ED25519 host key. >> debug1: Found key in /home/rshepard/.ssh/known_hosts:1 > > Found the public key. > That's the HOST (/etc/ssh) key to allow the 2 computers to connect. ssh only allows connections to TRUSTED hosts which it checks in file "known_hosts" This is NOT the key that allows login user authentication.
>> debug1: SSH2_MSG_SERVICE_ACCEPT received >> debug1: Authentications that can continue: publickey >> debug1: Next authentication method: publickey >> debug1: Trying private key: /home/rshepard/.ssh/id_rsa >> debug1: Trying private key: /home/rshepard/.ssh/id_dsa >> debug1: Trying private key: /home/rshepard/.ssh/id_ecdsa >> debug1: Trying private key: /home/rshepard/.ssh/id_ed25519 >> debug1: No more authentication methods to try. >> Permission denied (publickey). > > Not finding the public key. that's the USER login authentication key. The public key listed in DESTINATION authorized_keys does not match the PUBLIC key on the SOURCE computer. Either that, or you have /etc/ssh/sshd_config setup incorrectly for pub/private key authentication. (remember: the default Slackware install of sshd does not use keys at all. You login via normal username/password. See explanation on the other list thread.) http://docs.slackware.com/howtos:security:sshkeys http://docs.slackware.com/howtos:security:ssh -Ed _______________________________________________ PLUG mailing list [email protected] http://lists.pdxlinux.org/mailman/listinfo/plug
