Description of problem: Git access to AWS Code Commit repositories works fine under F32. Following upgrade to F33 access is not possible Version-Release number of selected component (if applicable): How reproducible: Every time and on a number of git respositories Steps to Reproduce: 1. 2. 3. Actual results: Permission denied (publickey). 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/xxxx/.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/xxxx/.ssh/id_rsa_aws_fred 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_fred RSA SHA256:<key_id> explicit debug1: send_pubkey_test: no mutual signature algorithm debug1: No more authentication methods to try. <userid>@git-codecommit.eu-west-1.amazonaws.com: Permission denied (publickey). Expected results: Git commands to work. Additional info: /etc/crypto-policies/back-ends/openssh.config seems to have removed some cyphers and this could be the cause of the issue.
Hi! First, I would like to ask if this bug report was intended for gsi-openssh (for which it was filed) or the standard openssh. I see no specific mention of GSI in neither the title or the description. The bug is a copy of bug #1890179 filed against openssh. If this was really intended for gsi-openssh, the solution is the same as for the openssh bug. The gsi-openssh uses the same default configuration (except for enabling GSI) and the same crypto policy as openssh. *** This bug has been marked as a duplicate of bug 1890179 ***