Bug 1890176

Summary:	Update from F32 to F33 has broken SSH access to AWS Cloud environments
Product:	[Fedora] Fedora	Reporter:	TR Bentley <home>
Component:	gsi-openssh	Assignee:	Mattias Ellert <mattias.ellert>
Status:	CLOSED DUPLICATE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	urgent	Docs Contact:
Priority:	unspecified
Version:	33	CC:	mattias.ellert
Target Milestone:	---
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-10-29 15:08:04 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description TR Bentley 2020-10-21 15:16:50 UTC

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.

Comment 1 Mattias Ellert 2020-10-29 15:08:04 UTC

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 ***