Pipe hashes to a file

[sergeevabc]

Windows 7 x64, sha256sum 2.0.4.

Source: sha256sum_20250612.zip

Проверка
├── birds.txt
├── pájaros.txt
├── rhash.exe
├── sha256sum01.exe
├── sha256sum02.exe   - di-mgt.com.au
├── sha256sum03.exe   - coreutils 6.11
├── sha256sum04.exe   - github.com/markpizz/HashSum (should be renamed to sha256sum.exe to work)
├── vögel.txt
├── птицы-vögel-pájaros-birds.txt
└── птицы.txt

sha256sum01 by @cwansart is the only sha256sum out of four you can find on the Internet that works with Unicode, great! But I still cannot pipe hashes to a file, because sha256sum01 *.txt > sums throws an error.

I do not know if only Windows 7 is affected, but I know for sure that it can be fixed, because rhash (written in C as well) can do that. It pipes hashes to a UTF8 file which can then be verified without issues.

$ rhash --sha256 *.txt > sums

$ file sums
sums: Unicode text, UTF-8 text, with CRLF line terminators

$ sha256sum01 -c sums
birds.txt: OK
pájaros.txt: OK
vögel.txt: OK
птицы-vögel-pájaros-birds.txt: OK
птицы.txt: OK

Oh, Christian! You are one step away from creating the perfect sha25sum. It's so exciting!

[apollo7321]

sha256sum01 by @cwansart is the only sha256sum out of four you can find on the Internet that works with #7, great! But I still cannot pipe hashes to a file, because sha256sum01 *.txt > sums throws an error.

So the problem is how Windows handles input. It uses UTF-16 at some places and you have to do weird conversions. I did some testing but I have nothing working yet and currently not that much time. I hope I can look at it in the next few days.

[apollo7321]

@sergeevabc you ran rhash in Bash or something like that?

I ran it on Windows and the same result. PowerShell 5 does some awful things with UTF8, so either use PwSh7 or cmd.

Out of couriosity I created a minimal program with Go in the go_port branch, see: https://github.com/cwansart/sha256sum.exe/tree/go_port
Would you like to test if this one will work on all your tests? https://github.com/cwansart/sha256sum.exe/actions/runs/15661737179/artifacts/3330566260

Here is the complete pipeline: https://github.com/cwansart/sha256sum.exe/actions/runs/15661737179/job/44120436934

[sergeevabc]

you ran rhash in Bash or something like that?

Usual cmd.exe of Windows 7. But rhash works the same way in Pwsh 7 too.

Out of couriosity I created a minimal program with Go
Would you like to test if this one will work on all your tests?

It works as expected.
Line terminators are LFs (Unix), not CRLFs (Windows), that's not the point right now.

$ sha256sum_go.exe *.txt > sums

$ file sums
sums: Unicode text, UTF-8 text

$ sha256sum_go.exe -c sums
птицы.txt: OK
birds.txt: OK
pájaros.txt: OK
vögel.txt: OK
птицы-vögel-pájaros-birds.txt: OK

$ rhash -c sums
--( Verifying sums )------------------------------------------------------------
birds.txt                                           OK
pájaros.txt                                         OK
vögel.txt                                           OK
птицы-vögel-pájaros-birds.txt                       OK
птицы.txt                                           OK
--------------------------------------------------------------------------------
Everything OK

[apollo7321]

Thank you for testing.

Usual cmd.exe of Windows 7. But rhash works the same way in Pwsh 7 too.

Okay, I wasn't sure if you were using $, so I thought you might be using Bash or something similar. I honestly have no idea why it crashes on Windows 7. There are other issues on Windows 11 as well, but no crashes.

It works as expected. Line terminators are LFs (Unix), not CRLFs (Windows), that's not the point right now.

Oh, my bad. I fixed it with this commit: 244c5ed
And here is the download: https://github.com/cwansart/sha256sum.exe/actions/runs/15700277926/artifacts/3342592109

$ sha256sum_go.exe *.txt > sums

$ file sums
sums: Unicode text, UTF-8 text

$ sha256sum_go.exe -c sums
птицы.txt: OK
birds.txt: OK
pájaros.txt: OK
vögel.txt: OK
птицы-vögel-pájaros-birds.txt: OK

Great to see that everything seems to work. I am thinking about switching from the C source code, which I initially started for an internal pipeline and as a "getting back into C" project. I really love that the size is just 23 KB, whereas the Go-based version is over 2 MB in size. But overall, I am much more confident with the Go version.