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.

Description of problem:
There have been some Technical Decisions for OSPP that allows a little more flexibility. We like a couple things amended to ease some restrictions:

sshd_config
Ciphers aes128- gcm, aes256-gcm
RekeyLimit change back to 1G

ssh_config
Ciphers aes128- gcm, aes256-gcm
RekeyLimit change back to 1G

Additional info:
I don't know how this is checked. If crypto policy does that and no changes are needed to support these changes, then feel free to close this bz.

*** This bug has been marked as a duplicate of bug 1813064 ***

Please note that sshd_rekey_limit is not handled by crypto policies.

Concerning sshd, as Matej said, we have rule sshd_rekey_limit, which is currently hardcoded to 512M 1h. We can change it or customize it with a variable.
We have no rule for configuring ssh client rekey limit but it should not be difficult to create one.

Rule for ssh client rekey limit is upstream:
https://github.com/ComplianceAsCode/content/pull/5788
The rule for ssh server rekey limit was adjusted to meet needs of this BZ here:
https://github.com/ComplianceAsCode/content/pull/5782

FTR, https://github.com/ComplianceAsCode/content/pull/5772 is also necessary for this BZ, as it prepares the rule to be parametrized.

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 (scap-security-guide 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-2020:4626