Arch Linux

Description:

There is a bug in the latest coreutils package that reports where checksuming files reports "OK" even if the checksum does not match. The bug only occurs if the checksum is the first of n.
I opened this bugreport to give visibility to this bug on official arch resources and to inform the [coreutils] maintainer of it so they can decide whether to backport the patch that fixes the bug (patch is linked in the bugreport).

This bug was reported first by user u/patenteng on reddit: https://redd.it/11zdecf
moviuro reposted it to the coreutils bugtracker: https://debbugs.gnu.org/cgi/bugreport.cgi?bug=62403

Additional info:
* package version(s): 9.2-1
* link to upstream bug report, if any: https://debbugs.gnu.org/cgi/bugreport.cgi?bug=62403

Steps to reproduce:
echo "123" > 1
echo "1234" > 2
echo "abc" > 3
sha256sum 1 2 3 > sums.sha256
# alter the second file
echo "123" > 2
sha256sum -c sums.sha256
tail -n 2 sums.sha256 | sha256sum -c

Gives:

1: OK
2: OK
3: OK
sha256sum: WARNING: 1 computed checksum did NOT match
2: FAILED
3: OK
sha256sum: WARNING: 1 computed checksum did NOT match