Bug 1712419

Summary:	libssh does not support PubkeyAcceptedKeyTypes option in configuration file
Product:	Red Hat Enterprise Linux 8	Reporter:	Anderson Sasaki <ansasaki>
Component:	libssh	Assignee:	Anderson Sasaki <ansasaki>
Status:	CLOSED ERRATA	QA Contact:	Ivan Nikolchev <inikolch>
Severity:	unspecified	Docs Contact:
Priority:	medium
Version:	8.0	CC:	inikolch, szidek
Target Milestone:	rc	Keywords:	Triaged
Target Release:	8.1	Flags:	pm-rhel: mirror+
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	libssh-0.9.0-4.el8	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-11-05 22:36:03 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 Anderson Sasaki 2019-05-21 13:07:02 UTC

Description of problem:
libssh ignores the PubkeyAcceptedKeyTypes option as defined for OpenSSH configuration file. Such option is present in the configuration file libssh loads by default.

In libssh the supported option with the same functionality is named PubkeyAcceptedTypes. One possible way to fix this is to make libssh to support PubkeyAcceptedKeyTypes as an alias for the existing PubkeyAcceptedTypes option.

Version-Release number of selected component (if applicable):
libssh-0.8.5-2

How reproducible:
always

Steps to Reproduce:
1. Use a configuration file containing the unsupported option PubkeyAcceptedKeyTypes. To be able to see the debug information, also set the LogLevel to be VERBOSE. For example, putting the following content in ~/.ssh/config:

LogLevel VERBOSE
PubkeyAcceptedKeyTypes rsa-sha2-256

2. Run an application which uses libssh and try to connect to a server

Actual results:
In one of the first lines of the output, libssh will print:

ssh_config_parse_line:  Unknown option: PubkeyAcceptedKeyTypes

Expected results:
No message such as the one above.

Additional info:

Comment 8 errata-xmlrpc 2019-11-05 22:36:03 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2019:3657