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:
Currently installed openssl.cnf contain the following section:

[default_sect] 
# activate = 1 

If there are no other provider sections, we load and activate the default provider according to documentation. 

If we add the legacy section and don't uncomment the activate=1 line, it makes impossible to login into the machine via ssh, because only legacy algorithms persisted enabled.

Version-Release number of selected component (if applicable):
3.0.0

How reproducible:
Always

Steps to Reproduce:
1. vim /etc/pki/tls/openssl.cnf
2. add 'legacy = legacy_sect' to [provider_sect] section
3. add a section 
[legacy_sect] 
activate = 1 
4. save the file
5. Try to ssh the machine

Actual results:
$ ssh hostname
kex_exchange_identification: read: Connection reset by peer
Connection reset by hostname port 22

Expected results:
Successful ssh to remote machine

Additional info:
Looks like we can't do anything to avoid this problem, but if we activate the default provider explicitly and add an explaining comment, it can help.

that's not correct way to enable legacy provider, so it breaking the system configuration is expected given the behaviour documented in upstream documentation

as such it's a duplicate of bug 1975836

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