# OpenSearch RPM distro SHA256 signatures

**URL:** <https://forum.opensearch.org/t/opensearch-rpm-distro-sha256-signatures/6180>\
**Category:** Build\
**Created:** [June 8, 2021, 11:42pm UTC](https://forum.opensearch.org/t/opensearch-rpm-distro-sha256-signatures/6180 "2021-06-08T23:42:18Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![justme](https://avatars.discourse-cdn.com/v4/letter/j/f0a364/32.png) [@justme](https://forum.opensearch.org/u/justme)\
**Post date:** [June 8, 2021, 11:42pm UTC](https://forum.opensearch.org/t/opensearch-rpm-distro-sha256-signatures/6180/1 "2021-06-08T23:42:18Z")

</div>

A problem I am battling with the Elastic repo’s are that they seem to not sign their RPM artifacts in their yum repos with SHA256 signatures. This causes problems on RHEL/Centos 8 machines that are in FIPS mode. The FIPS mode is required for compliance reasons. I realize this is a logstash bug, but I think there are similar issues with the other products in their yum repos ([Sign Logstash RPM w/ SHA256 header for FIPS-enabled Operating Systems · Issue #12597 · elastic/logstash · GitHub](https://github.com/elastic/logstash/issues/12597)). I am hoping that since OpenSearch is a more modern approach, that the packages will be signed with (kind of?) modern signature like SHA256. Does anyone associated with the RPM build planned for 1.0 GA have any insight on if that will be shipped with the RPM/yum repos at 1.0GA? Thanks in advance!

---

<div class="post-metadata">

**Author:** ![searchymcsearchface](https://sea1.discourse-cdn.com/flex019/user_avatar/forum.opensearch.org/searchymcsearchface/32/868_2.png) [@searchymcsearchface](https://forum.opensearch.org/u/searchymcsearchface)\
**Post date:** [June 9, 2021, 1:22pm UTC](https://forum.opensearch.org/t/opensearch-rpm-distro-sha256-signatures/6180/2 "2021-06-09T13:22:52Z")

</div>

@justme Interesting! I’ll be honest, I’m not sure what the plans are for this particular aspect of distribution, but it sounds like something that should be covered. I would post an issue on [https://github.com/opensearch-project/opensearch-build](https://github.com/opensearch-project/opensearch-build) to make sure this is covered.