Description of problem: debug1: Server host key: ssh-rsa SHA256:tKjRkOL8dmJyTmSbeSdN1S8F/f0iql3RlvqgTOP1UyQ debug1: Host 'git-codecommit.eu-west-1.amazonaws.com' is known and matches the RSA host key. debug1: Found key in /home/tim/.ssh/known_hosts:68 debug1: rekey out after 4294967296 blocks debug1: SSH2_MSG_NEWKEYS sent debug1: expecting SSH2_MSG_NEWKEYS debug1: SSH2_MSG_NEWKEYS received debug1: rekey in after 4294967296 blocks debug1: Will attempt key: /home/tim/.ssh/id_rsa_aws_trinity RSA SHA256:<key_id> explicit debug1: SSH2_MSG_SERVICE_ACCEPT received debug1: Authentications that can continue: publickey debug1: Next authentication method: publickey debug1: Offering public key: /home/tim/.ssh/id_rsa_aws_trinity RSA SHA256:<key_id> explicit debug1: send_pubkey_test: no mutual signature algorithm debug1: No more authentication methods to try. <user_id>@git-codecommit.eu-west-1.amazonaws.com: Permission denied (publickey). Version-Release number of selected component (if applicable): How reproducible: All the time on a number of GIT repositories. Steps to Reproduce: 1. Try to run git pull with a SSH connected repository 2. 3. Actual results: Permission denied (publickey) Expected results: a Git Pull Additional info:
Sorry for the multiple edits but Bugzilla crashes on screen saves\!
The server probably does not support SHA2 signatures. You'll have to switch to LEGACY policy. update-crypto-policies --set LEGACY
Thanks works a treat.
Related bug, assuming aws is using debian-derivative: https://bugzilla.redhat.com/show_bug.cgi?id=1881301
It would seem so and this is using AWS supported services so could impact a number of people.
*** Bug 1890176 has been marked as a duplicate of this bug. ***