authorized keys - ssh does not even access ~/.ssh/authorized_keys -
This is setup.
For 24 hours, password-less SSH worked for log-in fine. We used to use hours in hours.
Then I accidentally ordered this command to be ssh-keygen -e -f ~ / .ssh / id_rsa & gt; ~ / .ssh / id_dsa_com.pub
Since then my server can access the SFTP server without prompting for the password.
[user @ localserver .ssh] $ l Total 32 DWX ------ 2 user users 4096 January 22 09:24. Drwx ------ 4 user users 4096 Jan 22 09:24 .. -R-R - R--. 1 user user 742 January 21, 16:32 authorized_keys -rw -------. 1 user user 668 21 Jan 21:25 id_dsa -rw-r - r--. 1 user user 612 January 21 16:25 id_dsa.pub -rw -------. 1 user user 1675 Jan 21 16:39 ID_RCA-R-R-R-4. 1 user user 404 21 January 16:39 id_rsa.pub -rw-rw-rw-. 1 user user 252 January 21 16:21 Known_Hosts
When I turn on debugging using VVV, it also does not see my authorized_kiss file:
Authentication can continue that: publickey, password debug3: favorite gssapi-keyex, gssAPI-cum-mike, publickey, keyboard-affiliate, password debug3: authmethod_lookup publickey debug3: starting from the preferred balance, a separate list publickey, password Debug3 passed: keyboard-participant, password debug3: authmethod_ Is_enabled publickey debug1: Next authentication method: publickey debug1: Private key is trying: /home/user/.ssh/identity debug3: Any such identification: /home/user/.ssh/identity debug1: public offering key: / home /user/.ssh/id_rsa debug3: send_pubkey_test debug2: We sent a publickey packet, the responses can wait for debug3: certifications can continue that: publickey, password debug1: 384 bytes 1781 debug1 total written public key offer: / home / User / .ssh / id_dsa debug3: sending_aplica_stuff debug2: We sent a publisher packet, waiting for Answer: Debug3: can continue the authentication: publickey, password debug2: of 2309 debug1 total 528 bytes written authmethod_lookup password debug3: preferred balance: we did not send a packet, disabled method debug3, password debug3: authmethod_is_enabled password debug1: next authentication Method: Password
OK This is due to the ignorance of my SSB.
I sent them my pub key which is why the remote server was unable to accept my RSA pub because I "ruined" my RSA key.
So I made fresh RSA key, sent my pub keys, and voicemail, we are good to go.
Comments
Post a Comment