# Support for SHA256/SHA512 checksumming

**URL:** <https://forum.ansible.com/t/support-for-sha256-sha512-checksumming/16158>\
**Category:** Ansible Project\
**Created:** [September 9, 2014, 2:44pm UTC](https://forum.ansible.com/t/support-for-sha256-sha512-checksumming/16158 "2014-09-09T14:44:02Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Brantley\_West](https://avatars.discourse-cdn.com/v4/letter/b/b2d939/32.png) [@Brantley\_West](https://forum.ansible.com/u/Brantley_West)\
**Post date:** [September 9, 2014, 2:44pm UTC](https://forum.ansible.com/t/support-for-sha256-sha512-checksumming/16158/1 "2014-09-09T14:44:02Z")

</div>

I’m running into an issue using Ansible and MD5 checksumming on a FIPS compliant CentOS KVM system (ValueError: error:060800A3:digital envelope routines:EVP\_DigestInit\_ex:disabled for fips). Unfortunately FIPS-compliant systems/software typically disallow use of MD5 due to collision attack vulnerabilities. Is it possible to add support for SHA256 or SHA512 checksumming, and possibly make it the default option? I’m happy to write up a GitHub Issue if needed.

-bw

---

<div class="post-metadata">

**Author:** ![Michael\_DeHaan1](https://avatars.discourse-cdn.com/v4/letter/m/5e9695/32.png) [@Michael\_DeHaan1](https://forum.ansible.com/u/Michael_DeHaan1)\
**Post date:** [September 9, 2014, 3:44pm UTC](https://forum.ansible.com/t/support-for-sha256-sha512-checksumming/16158/2 "2014-09-09T15:44:50Z")

</div>

Basically referring to the logic to decide if a file needs to be transferred or not?

A GitHub issue doesn’t really do us a lot of good - Open Source is about itch scratching and the likelihood of someone else wanting to scratch your particular itch might be low - but a pull request would be interesting to see.

I’d probably expect to see something configurable in ansible.cfg