Bug 2155867

Summary:	enabling the legacy provider in openssl.cnf makes squid -k parse die with a SEGV
Product:	Red Hat Enterprise Linux 9	Reporter:	Walter Haidinger <whaidinger>
Component:	squid	Assignee:	Luboš Uhliarik <luhliari>
Status:	CLOSED MIGRATED	QA Contact:	rhel-cs-infra-services-qe <rhel-cs-infra-services-qe>
Severity:	low	Docs Contact:
Priority:	low
Version:	9.1	CC:	cllang, ddm
Target Milestone:	rc	Keywords:	MigratedToJIRA, Triaged
Target Release:	---	Flags:	pm-rhel: mirror+
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2023-09-21 22:34:30 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Walter Haidinger 2022-12-22 17:11:15 UTC

Description of problem:
Enabling the legacy provider in openssl.cnf makes "squid -k parse" die with a SEGV. 

Version-Release number of selected component (if applicable):
openssl-libs-3.0.1-43.el9_0.x86_64
squid-5.5-3.el9_1.x86_64

How reproducible: always (I think)
Reproduced in a fresh minimal install of RHEL 9.1/x64 in Virtualbox 7 but it was first noticed in a VM hosted by VMware vSphere 7.

Steps to Reproduce:
1. Enable (uncomment) the legacy provider in /etc/pki/tls/openssl.cnf

[provider_sect]
default = default_sect
legacy = legacy_sect
##
[default_sect]
activate = 1

[legacy_sect]
activate = 1

2. Try to parse squid config:
squid -k parse -f /etc/squid/squid.conf.default

Actual results:
...
2022/12/22 18:04:29| Initializing https:// proxy context
2022/12/22 18:04:29| Requiring client certificates.
Segmentation fault (core dumped)

Expected results:
No SEGV by squid -k parse

Additional info:
The actual squid config does not matter. 
Also throws a SEGV with an empty squid.conf.

Comment 1 Dmitry Belyavskiy 2023-01-23 16:35:10 UTC

Dear Walter,

Does squid introduce any atexit handlers?

Comment 2 Walter Haidinger 2023-01-31 09:56:17 UTC

No idea. We're just squid users and noticed the bug because we try to test the config before applying it via puppet.
The openssl legacy provider is required for a different software unrelated to squid.

Comment 3 Dmitry Belyavskiy 2023-01-31 09:58:37 UTC

Changing the component then.

Comment 4 Dustin Marquess 2023-08-03 22:59:04 UTC

Same happens with nmap when fed a script that uses openssl (eg, ssl-enum-ciphers.nse)

Comment 5 RHEL Program Management 2023-09-21 22:07:34 UTC

Issue migration from Bugzilla to Jira is in process at this time. This will be the last message in Jira copied from the Bugzilla bug.

Comment 6 RHEL Program Management 2023-09-21 22:34:30 UTC

This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.

Due to differences in account names between systems, some fields were not replicated.  Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.

To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "RHEL-" followed by an integer.  You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:

"Bugzilla Bug" = 1234567

In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information.