-
Story
-
Resolution: Unresolved
-
Normal
-
None
-
rhel-8.4.0
-
rhel-sst-cs-system-management
-
8
-
False
-
-
None
-
None
-
None
-
None
-
Enhancement
-
-
Proposed
-
-
All
-
None
1. Proposed title of this feature request
[RFE] Bacula FIPS compliant
2. What is the nature and description of the request?
Would like the Bacula packages provided in rhel-8-for-x86_64-appstream-rpms to operate under a FIPS enabled RHEL8 deployment
3. Why does the customer need this? (List the business requirements here)
We are a US Federal Government Agency Subject to DISA-STIG, we are required to use FIPS, if a package does not support FIPS we can not use it. RHEL8 is suppose to be FIPS 140-2 compliant, going for FIPS certification, but clearly Bacula, provided in the AppStream REPO is not.
https://www.redhat.com/en/blog/how-rhel-8-designed-fips-140-2-requirements
4. How would the customer like to achieve this? (List the functional requirements here)
Recompile the Bacula RPM's with FIPS compliant Cyphers (not MD5)
5. For each functional requirement listed, specify how Red Hat and the customer can test to confirm the requirement is successfully implemented.
6. Is there already an existing RFE upstream or in Red Hat Bugzilla?
NO
7. Does the customer have any specific timeline dependencies and which release would they like to target (i.e. RHEL5, RHEL6)?
RHEL 8.0
8. Is the sales team involved in this request and do they have any additional input?
NO
9. List any affected packages or components.
bacula-client.x86_64 9.0.6-6.el8 @rhel-8-for-x86_64-appstream-rpms
bacula-common.x86_64 9.0.6-6.el8 @rhel-8-for-x86_64-appstream-rpms
bacula-libs.x86_64 9.0.6-6.el8 @rhel-8-for-x86_64-appstream-rpms
Available Packages
bacula-console.x86_64 9.0.6-6.el8 rhel-8-for-x86_64-appstream-rpms
bacula-director.x86_64 9.0.6-6.el8 rhel-8-for-x86_64-appstream-rpms
bacula-libs-sql.x86_64 9.0.6-6.el8 rhel-8-for-x86_64-appstream-rpms
bacula-logwatch.noarch 9.0.6-6.el8 rhel-8-for-x86_64-appstream-rpms
bacula-storage.x86_64 9.0.6-6.el8 rhel-8-for-x86_64-appstream-rpms
10. Would the customer be able to assist in testing this functionality if implemented?
yes