mirror of
https://github.com/saltstack/salt.git
synced 2025-04-17 10:10:20 +00:00
3703fc5291
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 |
||
|---|---|---|
| .. | ||
| .keep | ||
| .template.jinja | ||
| 34658.fixed.md | ||
| 52289.fixed.md | ||
| 63063.fixed.md | ||
| 65018.fixed.md | ||
| 65193.fixed.md | ||
| 65589.fixed.md | ||
| 65670.fixed.md | ||
| 65691.fixed.md | ||
| 65692.fixed.md | ||
| 65752.fixed.md | ||
| 65777.fixed.md | ||
| 65824.fixed.md | ||
| 65938.changed.md | ||
| 65951.deprecated.md | ||
| 65954.fixed.md | ||
| 65990.fixed.md | ||
| 66004.security.md | ||