FIPS host support
cover FIPS host support
The patch here, and one sent to bitbake-devel together enable basic support for a FIPS-140 host system.
What was identified were a few users of md5, which is not allowed for any security part of the system. It can still be used to identify changes and similar non-security activities. (OE already uses sha256 for file integrity.)
In addition to this, it's possible that a recipe may attempt to use md5 during the build process. In oe-core, the only user is 'ovmf'. At this time I don't intend to provide a fix for ovmf, but everything else in core works properly now.
Mark Hatle (1):
insane.bbclass: Update insane.bbclass to work on FIPS enabled hosts
meta/classes/insane.bbclass | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
Signature · 1 line
2.25.1
PATCH 1/1 insane.bbclass: Update insane.bbclass to work on FIPS enabled hosts
hashlib.md5() is not permitted on a FIPS enabled host system. This is due to md5 not being an approved hash algorithm.
Instead use:
hashlib.new('MD5', usedforsecurity=False)
This is allowed, as it's clear the hash is used for a non-security purpose.
Using an md5 to identify when a license has changed is permitted, as we're not using it for file integrity.
--- meta/classes/insane.bbclass | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
meta/classes/insane.bbclass +1 -1
@@ -549,7 +549,7 @@ python populate_lic_qa_checksum() { import hashlib lineno = 0 license = [] - m = hashlib.md5() + m = hashlib.new('MD5', usedforsecurity=False) for line in f: lineno += 1 if (lineno >= beginline):
Signature · 1 line
2.25.1