Bug 2021903

Summary:	stunnel: FTBFS with OpenSSL 3.0.0
Product:	[Fedora] Fedora	Reporter:	Sahana Prasad <sahana>
Component:	stunnel	Assignee:	Red Hat Crypto Team <crypto-team>
Status:	CLOSED WORKSFORME	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	rawhide	CC:	cllang, crypto-team, ngompa13, sahana, tm
Target Milestone:	---	Keywords:	Triaged
Target Release:	---	Flags:	fedora-admin-xmlrpc: mirror+
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2022-01-28 11:43:09 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:
Bug Depends On:
Bug Blocks:	1825937, 1992484

Description Sahana Prasad 2021-11-10 12:11:41 UTC

This bug is used to track the readiness of stunnel with OpenSSL 3.0.0.

Currently the build fails to build with OpenSSL 3.0.0 with the following logs
Task info: https://koji.fedoraproject.org/koji/taskinfo?taskID=78020255

Kindly fix them to ensure this package builds with OpenSSL 3.0.0

You can treat the deprecated warnings not as errors if you want to continue to use deprecated functions, but it is encouraged to use the new APIs, and this migration could be done sooner than later.

To not treat deprecated warnings as errors, you may use
-Wno-error=deprecated-declarations

To port to new APIs, kindly refer to the OpenSSL upstream migration guide:
https://www.openssl.org/docs/manmaster/man7/migration_guide.html

Thank you

Comment 1 Clemens Lang 2022-01-28 11:43:09 UTC

It seems this has been fixed meanwhile. I can no longer reproduce it with stunnel-5.58-4.fc36, and stunnel has been updated to 5.62-1, which also built correctly against OpenSSL 3.
The latest build on Koji is also green: https://koji.fedoraproject.org/koji/buildinfo?buildID=1901224.

I am closing this as WORKSFORME. Please re-open if you still see this problem.