First, thanks for reporting. This issue is fixed in Git and the fix will come with v1.2.7 release.
Being a bug from user's point of view, actually this issue is due to half-implemented sha256/sha512 support - without hash verification. So up to this point the issue concerns all previous RHash version. In more details. RHash up to v1.2.6 can't uniquely identify a hash function by hash length, so it supposed that all 128-bit hashes are MD5 or ED2K all 256-bit hashes are GOST R 34.11-94 hash all 512-bit hashes are Whirlpool Now the parsing of hash files and verification code was rewritten. If the program can't detect the precise hash function for say a 256-bit hash, then the program will calculate all supported 256-bit hashes and verify the hash value against all of them. To speed up verification, user can now specify exact hash function at command line.
signature.asc
Description: OpenPGP digital signature
