You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The Elasticsearch Curator RPM package (elasticsearch-curator-5.8.4-1.x86_64.rpm) should contain a SHA256-based Digest signature.
Actual Behavior
Without a SHA256 Digest signature, installation will fail on a FIPS 140-2 compliant EL8 host.
Steps to Reproduce the Problem
Attempt to install elasticsearch-curator-5.8.4-1.x86_64.rpm on a FIPS-enabled RHEL 8 host.
Installation fails with a "Transaction Test Error" message (does not verify: no digest).
To verify that there is no SHA256 Digest value, execute rpm --checksig --verbose elasticsearch-curator-5.8.4-1.x86_64.rpm -- note no SHA256 Digest value, only SHA1 and MD5 (the same issue exists with Logstash RPMs, but Elasticsearch and Kibana RPMs have the SHA256 Digest value..).
Specifications
Version: 5.8.4-1
Platform: x86_64
Subsystem:
Context (Environment)
Outside of manual installation via the rpm command with the --nodigest flag, we can't utilize our existing pipelines and automation logic to simply pull packages from a YUM repository on RHEL 8 hosts with FIPS 140-2 compliance mode enabled. I'd like to do it cleanly as opposed to with a workaround. Given that this has been implemented with Elasticsearch and apparently Kibana, hopefully the internal packaging teams can figure this out for Curator and Logstash.
Please implement SHA256 Digest signature support in Elasticsearch Curator packaging pipelines (and pass the above-referenced Issue along to the Logstash team, if there is internal communication on these types of things).
The text was updated successfully, but these errors were encountered:
Sorry you've had a hard time. Subsequent releases of Curator will not use RPM or DEB packaging at all (Docker or pip only), so this is unlikely to be addressed.
Expected Behavior
The Elasticsearch Curator RPM package (elasticsearch-curator-5.8.4-1.x86_64.rpm) should contain a SHA256-based Digest signature.
Actual Behavior
Without a SHA256 Digest signature, installation will fail on a FIPS 140-2 compliant EL8 host.
Steps to Reproduce the Problem
rpm --checksig --verbose elasticsearch-curator-5.8.4-1.x86_64.rpm
-- note no SHA256 Digest value, only SHA1 and MD5 (the same issue exists with Logstash RPMs, but Elasticsearch and Kibana RPMs have the SHA256 Digest value..).Specifications
Context (Environment)
Outside of manual installation via the
rpm
command with the--nodigest
flag, we can't utilize our existing pipelines and automation logic to simply pull packages from a YUM repository on RHEL 8 hosts with FIPS 140-2 compliance mode enabled. I'd like to do it cleanly as opposed to with a workaround. Given that this has been implemented with Elasticsearch and apparently Kibana, hopefully the internal packaging teams can figure this out for Curator and Logstash.For reference
Detailed Description
Please implement SHA256 Digest signature support in Elasticsearch Curator packaging pipelines (and pass the above-referenced Issue along to the Logstash team, if there is internal communication on these types of things).
The text was updated successfully, but these errors were encountered: