Create vision how to handle Perl modules in case of crypto-policies #19

Open
opened 2024-05-31 12:52:15 +00:00 by pbokoc · 0 comments
pbokoc commented 2024-05-31 12:52:15 +00:00 (Migrated from gitlab.com)

(Migrated from https://bugzilla.redhat.com/show_bug.cgi?id=2060893)

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.

(Migrated from https://bugzilla.redhat.com/show_bug.cgi?id=2060893) 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.
Commenting is not possible because the repository is archived.
No labels
No milestone
No project
No assignees
1 participant
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
docs-archive/sysadmin-guide#19
No description provided.