Bug 2060893 - Create vision how to handle Perl modules in case of crypto-policies
Summary: Create vision how to handle Perl modules in case of crypto-policies
Keywords:
Status: CLOSED DEFERRED
Alias: None
Product: Fedora Documentation
Classification: Retired
Component: technical-notes
Version: devel
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Michal Josef Spacek
QA Contact: Fedora Docs QA
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-03-04 13:07 UTC by Michal Josef Spacek
Modified: 2024-05-31 12:52 UTC (History)
3 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2024-05-31 12:52:58 UTC
Embargoed:

Attachments (Terms of Use)

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.
Note You need to log in before you can comment on or make changes to this bug.