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.
Bug 2020346 - Update the OSPP ssh settings
Summary: Update the OSPP ssh settings
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: crypto-policies
Version: 8.5
Hardware: Unspecified
OS: Unspecified
medium
low
Target Milestone: rc
: ---
Assignee: Alexander Sosedkin
QA Contact: Ondrej Moriš
URL:
Whiteboard:
Depends On:
Blocks: 1940119
TreeView+ depends on / blocked
 
Reported: 2021-11-04 16:07 UTC by Steve Grubb
Modified: 2022-05-10 16:38 UTC (History)
1 user (show)

Fixed In Version: crypto-policies-20211116-1.gitae470d6.el8
Doc Type: No Doc Update
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-05-10 15:22:45 UTC
Type: Bug
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker CRYPTO-5312 0 None None None 2021-11-15 16:44:54 UTC
Red Hat Issue Tracker RHELPLAN-101772 0 None None None 2021-11-04 23:12:20 UTC
Red Hat Product Errata RHBA-2022:2044 0 None None None 2022-05-10 15:22:50 UTC

Description Steve Grubb 2021-11-04 16:07:33 UTC 
Description of problem:
The ssh crypto requirements allowed by OSPP have been updated by NIAP. We can now make the following adjustments:

FCS_SSH_EXT.1.2 - public key authentication - add: ecdsa-sha2-nistp521 & ssh-ed25519

FCS_SSH_EXT.1.6: Key exchange methods - add: Diffie-hellman-group14-sha256, Diffie-hellman-group15-sha512, Diffie-hellman-group16-sha512, Diffie-hellman-group17-sha512, Diffie-hellman-group18-sha512, Curve25519-sha256

FCS_SSH_EXT.1.8: Rekeying - Update to 1Gb (sshd default?)


Additional info:
https://www.niap-ccevs.org/Profile/Info.cfm?PPID=459&id=459
Comment 2 Alexander Sosedkin 2021-11-12 13:47:08 UTC 
(I'm pretty sure I've composed this comment before on 2021-11-09 and something ate it. Sorry.)

Curve 25519 isn't enabled in plain FIPS, so let's not exclude it.

Diffie-hellman-group15-sha512, Diffie-hellman-group17-sha512 --- I don't even think openssh has support for them.

Crypto-policies doesn't control rekeying limits.

With that in mind, can we limit the request to just enabling ecdsa-sha2-nistp521, diffie-hellman-group14-sha256, diffie-hellman-group16-sha512, diffie-hellman-group18-sha512?
Comment 3 Steve Grubb 2021-11-12 14:23:37 UTC 
The intention is to enable what we have and not request new stuff to be coded up. So yes, we can limit what's enabled.
Comment 5 Ondrej Moriš 2021-11-16 16:36:05 UTC 
(In reply to Steve Grubb from comment #0)

> FCS_SSH_EXT.1.8: Rekeying - Update to 1Gb (sshd default?)

Steve, since this is out of scope of crypto-policies, do you think we need a bug for openssh for this? Or will it be handled via OSPP SCAP remediation (if there is something like that)?
Comment 6 Steve Grubb 2021-11-16 16:42:23 UTC 
If this is not set by crypto policy, then it's probably a SCAP setting.

Btw, we will need a similar update for RHEL 9, but openssh and openssl are newer and may allow even more options. I don't think we have done the analysis yet to see what rhel9 should have.
Comment 7 Alexander Sosedkin 2021-11-16 16:51:59 UTC 
Yeah, the subset of the changes controlled by crypto-policies went through rawhide and 9 first,
and I'm only now backporting them to 8.6,
on the general basis of not regressing on updates.

If in 9 FIPS:OSPP can be brought even closer to FIPS than in 8.6 --- glad to hear that,
I'll wait for the analysis and a RHEL-9 bug, then relax 9's OSPP even further if possible.
Comment 8 Steve Grubb 2021-11-16 16:55:13 UTC 
Bug 2023842 was filed for the SCAP changes.
Comment 13 errata-xmlrpc 2022-05-10 15:22:45 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 (crypto-policies bug fix and enhancement update), 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-2022:2044
Note You need to log in before you can comment on or make changes to this bug.