Open jsmeix opened 5 months ago
As it seems in practice no ReaR user was hit by it (because noone reported it up to now here) I think we can safely fix this issue later as time permits after the ReaR 3.0 release.
See starting at https://github.com/rear/rear/issues/3194#issuecomment-2175841475 about what we think what the intended use case of the OpalPBA code in ReaR likely is.
Nevertheless plain installing 'sedutil' on a system without a TCG Opal 2-compliant Self-Encrypting Disk should not make a normal "rear mkrescue" fail so the current OpalPBA code in ReaR needs some cleanup and enhancement.
@jsmeix good catch and I totally agree with you that just having the sedutil-cli
shouldn't have any impact on ReaR. I'd also say that the error message is more than just confusing, it seems rather misleading.
On openSUSE Leap 15.5 I installed the sedutil RPM which provides /usr/sbin/sedutil-cli
Having this program makes normal "rear mkrescue" with
fail:
From the debug log:
The reason is that the OpalPBA code in ReaR gets activated by the existence of any program called 'sedutil-cli':
see usr/share/rear/prep/default/380_include_opal_tools.sh Sigh :-(
Workaround to run ReaR normally: