# Release Checksums

**URL:** <https://discourse.imfreedom.org/t/release-checksums/272>\
**Category:** IMFreedom\
**Tags:** news\
**Created:** [April 30, 2025, 10:11pm UTC](https://discourse.imfreedom.org/t/release-checksums/272 "2025-04-30T22:11:34Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![grim](https://yyz1.discourse-cdn.com/flex007/user_avatar/discourse.imfreedom.org/grim/32/4_2.png) [@grim](https://discourse.imfreedom.org/u/grim)\
**Post date:** [April 30, 2025, 10:11pm UTC](https://discourse.imfreedom.org/t/release-checksums/272/1 "2025-04-30T22:11:34Z")

</div>

So… i just learned that if i use a `.sha256` file extensions, bash will complete the filename when tab’n for the `sha256sum` command… i’ve been using a `.sha256sum` extension for all of our releases.

I’m going to assume this means no one is testing them that way (if at all) since no one has mentioned it..

At any rate, going forward they will have a `.sha256` extension.

---

<div class="post-metadata">

**Author:** ![grim](https://yyz1.discourse-cdn.com/flex007/user_avatar/discourse.imfreedom.org/grim/32/4_2.png) [@grim](https://discourse.imfreedom.org/u/grim)\
**Post date:** [April 30, 2025, 11:21pm UTC](https://discourse.imfreedom.org/t/release-checksums/272/2 "2025-04-30T23:21:37Z")

</div>

I just realized meson is spitting out the checksums with `.sha256sum` extensions.. guess I should ask them about that or maybe getting the bash competitions tweaked is a better idea…