Bacula needs MD5 for some things, but normally it uses its own implementation. It looks like RHEL includes a patch bacula-9.0.6-use-crypto-from-openssl.patch to make it use the OpenSSL implementation of MD5, which leads to this error if you have a FIPS OpenSSL.
So the question is, can you still be meet your requirements if something in your system uses MD5? If the answer is no, then I think you can't use Bacula. Otherwise, building your own Bacula from the original source should fix it (or possibly rebuilding the RHEL rpms without that patch). __Martin >>>>> On Wed, 4 Dec 2024 15:13:00 -0500, Matthew Brown said: > > Greetings, > > RHEL 8 > bacula-client 9.0.6-6 > bacula-storage 9.0.6-6 > While performing one of the btape test commands: > > btape -c bacula-sd.conf /dev/nst0 > > I receive: > > Tape block granularity is 1024 bytes. > ERROR TERMINATION at parse_conf.c:567 > MD5 computation failed: disabled for FIPS > > FIPS is a requirement. Can my current environment be modified to use a > FIPS-compliant method in bacula? Compiling a more recent version is a > possibility if modification is not possible and that would resolve the > error. > > Thank you > _______________________________________________ Bacula-devel mailing list Bacula-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-devel
