Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
DescriptionStanislav Zidek
2019-01-22 12:49:56 UTC
Description of problem:
Looking to e.g. man sshd_config, part Ciphers, it is documenting wrong default value:
Ciphers
...
The supported ciphers are:
...
The default is:
chacha20-poly1305,
aes128-ctr,aes192-ctr,aes256-ctr,
aes128-gcm,aes256-gcm
This might be confusing to administrators, because true defaults are dependent on current policy profile.
Version-Release number of selected component (if applicable):
# rpm -q openssh crypto-policies
openssh-7.8p1-4.el8.x86_64
crypto-policies-20181217-1.git9a35207.el8.noarch
Additional info:
Actual config files (sshd_config and ssh_config) DO mention crypto policies.
I do not understand why this is assigned to crypto-policies.
And I do not think we should document in crypto-policies manual pages the exact list of algorithms for each and every crypto back end that is configured by crypto-policies. That makes completely no sense as the users can look into the individual config files at what the list is and duplicating this info in manual pages only complicates things.
Can you please clarify, what you request here?
We should fix this one too as described in bug #1625318. The proposal is to add to ssh_config and sshd_config manual pages something like this:
The default is handled by system-wide crypto-policies(7). How to overwrite this default, see manual page update-crypto-policies(8).
instead of
The default is:
chacha20-poly1305,
aes128-ctr,aes192-ctr,aes256-ctr,
aes128-gcm,aes256-gcm
I propose to change this in each of Ciphers, MACs, KexAlgorithms, GSSAPIKexAlgorithms, PubkeyAcceptedKeyTypes, HostKeyAlgorithms (in server only so far).
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/RHSA-2019:3702
Description of problem: Looking to e.g. man sshd_config, part Ciphers, it is documenting wrong default value: Ciphers ... The supported ciphers are: ... The default is: chacha20-poly1305, aes128-ctr,aes192-ctr,aes256-ctr, aes128-gcm,aes256-gcm This might be confusing to administrators, because true defaults are dependent on current policy profile. Version-Release number of selected component (if applicable): # rpm -q openssh crypto-policies openssh-7.8p1-4.el8.x86_64 crypto-policies-20181217-1.git9a35207.el8.noarch Additional info: Actual config files (sshd_config and ssh_config) DO mention crypto policies.