Bug 1459215 - ssh -Q key not listing rsa-sha2-256 and rsa-sha2-512
Summary: ssh -Q key not listing rsa-sha2-256 and rsa-sha2-512
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: openssh
Version: 7.4
Hardware: Unspecified
OS: Unspecified
low
unspecified
Target Milestone: rc
: ---
Assignee: Jakub Jelen
QA Contact: BaseOS QE Security Team
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-06-06 14:40 UTC by Stefan Dordevic
Modified: 2019-02-12 09:44 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-02-11 15:39:23 UTC
Target Upstream Version:


Attachments (Terms of Use)

Description Stefan Dordevic 2017-06-06 14:40:48 UTC
Description of problem:

"ssh -Q key" command is not listing 
rsa-sha2-256 and rsa-sha2-512

# ssh -Q key
ssh-ed25519
ssh-ed25519-cert-v01
ssh-rsa
ssh-dss
ecdsa-sha2-nistp256
ecdsa-sha2-nistp384
ecdsa-sha2-nistp521
ssh-rsa-cert-v01
ssh-dss-cert-v01
ecdsa-sha2-nistp256-cert-v01
ecdsa-sha2-nistp384-cert-v01
ecdsa-sha2-nistp521-cert-v01

If we introduce them in the man pages, even if they are part of extension I guess they also should be listed from command line with "ssh -Q key"

Version-Release number of selected component (if applicable):
openssh-7.4p1-11.el7

Comment 1 Simo Sorce 2019-02-11 15:39:23 UTC
This issue was not selected to be included either in Red Hat Enterprise Linux 7.7 because it is seen either as low or moderate impact to a small amount of use-cases. The next release will be in Maintenance Support 1 Phase, which means that qualified Critical and Important Security errata advisories (RHSAs) and Urgent Priority Bug Fix errata advisories (RHBAs) may be released as they become available. We will now close this issue, but if you believe that it qualifies for the Maintenance Support 1 Phase, please re-open; otherwise we recommend moving the request to Red Hat Enterprise Linux 8 if applicable.

Comment 2 Jakub Jelen 2019-02-12 09:44:58 UTC
This is intentional. Those aren't key types but signature algorithms and may be listed using "ssh -Q sig"

Changing the close resolution to be clear.


Note You need to log in before you can comment on or make changes to this bug.