Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 2060893

Summary:	Create vision how to handle Perl modules in case of crypto-policies
Product:	[Retired] Fedora Documentation	Reporter:	Michal Josef Spacek <mspacek>
Component:	technical-notes	Assignee:	Michal Josef Spacek <mspacek>
Status:	CLOSED DEFERRED	QA Contact:	Fedora Docs QA <docs-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	devel	CC:	pbokoc, wb8rcr, zach
Target Milestone:	---
Target Release:	---
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:	2024-05-31 12:52:58 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 Michal Josef Spacek 2022-03-04 13:07:53 UTC

We have Perl modules in Fedora, which are implementing security algorithms directly (in C or Perl).
This mean, that we cannot control functionality by crypto-policies.

We need to create some vision how this situation handle.

Output should be a document, which describe actual situation and suggests real solutions which fix this situation.

Comment 1 Petr Bokoc 2024-05-31 12:52:58 UTC

Hi, I'm trying to get the whole Fedora Documentation product in BZ closed, so I migrated the bug to the issue tracker in Gitlab at https://gitlab.com/fedora/docs/fedora-linux-documentation/fedora-linux-sysadmin-guide/-/issues/19.