-
Notifications
You must be signed in to change notification settings - Fork 4.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Sign Beats RPMs w/ SHA256 header for FIPS-enabled Operating Systems #23670
Comments
Pinging @elastic/agent (Team:Agent) |
There is currently some work ongoing in Elasticsearch, see elastic/elasticsearch#75731 and the related issues / pull requests. We need to figure out we make this best happen as part of the build process. |
just for clarification. I think apart from the sha256 header digest also sha256 payload digest. Furthermore file digest needs to be switched from md5 (rpm default) to sha256. how are the beats rpms currently build? ES is using the nebula ospackage plugin which relies on redline, a java library for building rpms. We needed to patch this redline library to get sha256 header and sha256 payload + file digests in our ES RPMS |
The RPMs from beats are built using fpm. FPM does have an beats/dev-tools/mage/pkgtypes.go Lines 712 to 758 in 5481b06
|
Does this look like what we want?
I updated the FPM container image to include rpm 4.14.2 (it had 4.12). And then I added |
Here's the update for FPM: elastic/golang-crossbuild#118 |
@andrewkroh that looks good IMO. For elasticsearch we have this output for the rpm I've tested succesfully on centos tips enabled:
|
one thing I also needed to change is to use filedigestalgo to sha256 (defaults to md5) to get our rpm working. You should be able to test the RPM on one of our centos 8 fips enabled CI images |
And this is the change to Beats to add the |
Describe the enhancement:
Beats RPMs will fail to install on RHEL 8 w/ FIPS mode enabled because the RPMs aren't signed with a SHA256 header (see
BZ#1581990
[1].It's possible to get around this by installing with
--nodigest --nofiledigest
arguments [2], but such a workaround may not be acceptable for certain organizations.[1] https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/8/html-single/8.0_release_notes/index
[2] https://access.redhat.com/solutions/4460971
The text was updated successfully, but these errors were encountered: