Company
Date Published
Author
Maxime Greau
Word count
660
Language
-
Hacker News points
None

Summary

In response to increased security concerns following a SHA-1 collision announcement, Elastic Stack has transitioned to using SHA-512 cryptographic hashes for verifying the integrity of its binary artifacts, despite continuing to provide SHA-1 checksums for backward compatibility with older versions. With the release of Elastic Stack 5.6.2, both SHA-1 and SHA-512 checksum files were available, but starting from version 6.0.0, only SHA-512 checksums are generated, featuring a more user-friendly format that combines the hash value and the associated filename on the same line. This change aims to enhance security and streamline the process of verifying downloaded files. Elasticsearch has also updated its plugin installation component to support SHA-512 checksums, requiring official plugins to adhere to this format, while community plugins can still use SHA-1 until it is phased out in future updates. Users are encouraged to update their verification scripts to accommodate these new SHA-512 files to ensure continued file integrity checks for Elastic Stack releases.