1970.01.01@00.00:00

[ahmedov-arsen]

В любом файле дата определяется неправильно
Ниже пример файла .md5

Generated by OpenHashTab v3.0.4 at 2024-06-13T10:38:57Z

https://github.com/namazso/OpenHashTab/

#md5#Скрин версии 1.14.png#1970.01.01@00.00:00
DE4B03B2E5A8534A4D770273AE1BB86B *Скрин версии 1.14.png

[desk7]

I have the same issue. In the exported checksum, the date is always 1970.01.01@00.00:00.

The issue happens both in a windows 10 machine and in a windows 11 machine.

[namazso]

This is (or at least was) an intentional design choice, as the original cors checksum software (from where this format comes) is broken and uses local time instead of UTC time. It also uses these timestamps for hash updates, therefore moving timezones can skip hashing or cause false corruptions. Therefore, OpenHashTab just writes 1970 to ensure the timestamp is never mistakenly in the future when interpreted in local time.

Do you have any suggestions as to what would be a better behavior?

[ahmedov-arsen]

Тогда лучше не выводить дату совсем, чем показывать неправильное