Ted

The current poll is asking users if they would be interested in a code-signed version of QuickHash. Of the votes cast so far, several people have answered with "I don't understand the question" so, I hope to try and make it clearer. In recent times, operating systems like Windows 10, Apple Mac OSX and malicious software detection tools like AVG, Kaspersky, Norton and Windows Defender take a dim view of executable files that are "not signed". What this means is that the operating system cannot be sure sure that the program being run is safe, because it does not [...]

v2.8.3 had a bug introduced that was not present in v2.8.2 or below and has been fixed in v.2.8.4. The bug related to the text hashing tab. Text was not being hashed correctly due to a change in the code that unknowingly had an adverse effect on the computed hash. Any user who used v2.8.3 to hash text values should re-run their computations using the new version and my apologies come with this. No other part of the program was affected. Due to the severity of this bug, I have removed v2.8.3 from the available downloads to avoid wider [...]

A user has reported an issue with v2.8.3 (http://34.225.163.28/bugs/expected-hash-value-report-wrongly-on-single-file-hashing/) regarding a peculiarity with the "Expected Hash Value" field. This field was added a while ago, but another user requested that if the expected hash value is pasted after the file was hashed (whereas it was designed to be input before the file was hashed), the file had to be hashed again in order to compare it to the expected hash value that the user had pasted earlier. So, to fix that, a change was added in v2.8.3 such that if the value was pasted after the file had been hashed, [...]