salt/changelog/65589.fixed.md
Skyler Hawthorne 3703fc5291 fix incorrect hash type result in s3fs
The s3fs backend is currently computing the incorrect hash type. The
default hashing algorithm was changed from md5 to sha256. The s3 backend
calls the hashing function without specifying the hash algorithm,
and then hardcodes the result's hash type to md5. After the change to
sha256, this means it was computing a sha256 sum, but saying it was md5.
In turn, it would compute the sha256 sum of the existing target file
and compare it to the cached file's md5, which would obviously always
be different.

This causes downstream effects, such as test mode always reporting a
change, even when there isn't one.

Fixes #65589
2024-02-13 21:38:54 +00:00

82 B

Fixes the s3fs backend computing the local cache's files with the wrong hash type