gpfjeff/winhasher

Free cryptographic file hash generator for Windows (.NET 2.0)

winhasher's Issues

Release date estimation?

I see some commit activity, but yet...

Current Release 1.6.2.67
Date of Release August 6, 2013

When can we expect a release of a new version, roughly?

Winhasher has always been a must-have utility for me ;-)

Output redirection

What steps will reproduce the problem?
1. Try running the command with output redirection

What is the expected output? What do you see instead?
Expect output in file but get error instead.
W:\Apps\WinHasher>1> filehash.txt M:\Apps\WinHasher\hash.exe -sha512 -base64 "M:
\Apps\WinHasher\cmdhelp.html"

W:\Apps\WinHasher>type filehash.txt

Computing SHA-512 of M:\Apps\WinHasher\cmdhelp.html...   0%
ERROR: No file was specified (the file path was empty, contained only white spac
e, or contained invalid characters).

WinHasher v. 1.6.0.43

or

W:\Apps\WinHasher>M:\Apps\WinHasher\hash.exe -sha512 -base64 "M:\Apps\WinHasher\
cmdhelp.html" > filehash.txt

W:\Apps\WinHasher>type filehash.txt

Computing SHA-512 of M:\Apps\WinHasher\cmdhelp.html...   0%
ERROR: No file was specified (the file path was empty, contained only white spac
e, or contained invalid characters).

WinHasher v. 1.6.0.43

What version of the product are you using? On what operating system?
1.6.0.43

Please provide any additional information below.

Original issue reported on code.google.com by [email protected] on 15 Jun 2011 at 1:48

Hash comparison result not updated on subsequent calculations

What steps will reproduce the problem?
1. Compute the hash for a file and paste the correct expected value into the 
"Compare to:" field.  The result indication turns green with the text "Hashes 
match".
2. Select a new file and again compute the hash; do not update the "Compare 
to:" field.


What is the expected output? What do you see instead?
> Expected output = The new hash value is compared to the existing contents of 
the "Compare to:" field.  Since the new hash is based on a different file and 
the hash values won't match, the result indicator turns red with the text 
"Hashes do not match".
> Actual output = The result indicator remains green with the text "Hashes 
match".  Once the contents of the "Compare to:" field are modified, the hash 
values are compared and the correct result is provided.


What version of the product are you using? On what operating system?
> Version = 1.6
> OS = Win XP SP3


Please provide any additional information below.
> N/A

Original issue reported on code.google.com by [email protected] on 11 Apr 2012 at 6:14

Version 1.6.1 compiled with wrong build target

I recently received the following email from a user:

"However, your last compilation, 1.6.1 (which was the first I´ve tested) was 
actually compiled with .net framework 4.0 and not 2.0. I realized that after 
trying to use it in an old standalone XP computer and getting a warning popup. 
After that, I also downloaded 1.6.0 compilation which worked fine on the same 
machine.
 
I don´t know what was the change log from version 1.6 to 1.6.1, but I bet if 
you did it was for a good reason J. That said, is it possible to re-compile the 
latest version to your website using net 2.0 ? I do not have visual studio and 
would be much appreciate of that."

This is definitely a bug, albeit a minor one. Visual Studio allows you to 
target specific .NET versions in the project configuration file, but VS 2010 
defaults to .NET 4.0. This is easy enough to fix and I thought I did this 
already, but I may be confusing this with Cryptnos, which I know has had a 
release since WinHasher has.

Besides, I still haven't pushed out the fix for Issue 5 (oops), so I might as 
well get on it.

One caveat: I recently upgraded InnoSetup, and in doing so they cut off support 
for versions of Windows prior to XP. This is more Microsoft's doing than the 
InnoSetup team's, but that also means the new installer will not support 
anything prior to XP.

Original issue reported on code.google.com by [email protected] on 13 Jun 2013 at 10:48

Send To context menu is not working properly

What steps will reproduce the problem?

1. Install WinHasher 1.6.1.65.
2. Right click on a plain text file on Desktop and choose Send To and then 
WinHasher.

What is the expected output? What do you see instead?

Expected output: The chosen file data should be sent to WinHasher for 
generating messages digest (hash value).

Produced output: The chosen file is just copied to a directory at 
%appdata%\Microsoft\Windows\SendTo\WinHasher

What version of the product are you using? On what operating system?

WinHasher 1.6.1.65
Windows Vista Ultimate SP2 64-bit

Please provide any additional information below.

- Swedish Windows locale.
- Computer restart was not performed after installation.

Original issue reported on code.google.com by [email protected] on 20 Jan 2013 at 11:07

Attachments:

• [winhasher 1.6 bug screen 1.png](https://storage.googleapis.com/google-code-attachments/winhasher/issue-5/comment-0/winhasher 1.6 bug screen 1.png)
• [winhasher 1.6 bug screen 2.png](https://storage.googleapis.com/google-code-attachments/winhasher/issue-5/comment-0/winhasher 1.6 bug screen 2.png)
• [winhasher 1.6 bug screen 3.png](https://storage.googleapis.com/google-code-attachments/winhasher/issue-5/comment-0/winhasher 1.6 bug screen 3.png)
• [winhasher 1.6 bug screen 4.png](https://storage.googleapis.com/google-code-attachments/winhasher/issue-5/comment-0/winhasher 1.6 bug screen 4.png)

.Net 2.0 required

What steps will reproduce the problem?
running windows installer

What is the expected output? What do you see instead?
expected: installs, runs; seen: neither.

What version of the product are you using? On what operating system?
v1.6.2.67 from installer on Windows 11

Please provide any additional information below.
Issue: wouldn't install with
.Net
4.0.0.0
4.8.04161
5.0
installed, needed the .Net 2.0, as stated in Version 1.7 (!) of the README.txt. Unfortunately, the installer is providing a 1.6.... version.
Please: Build an installer for version 1.7, stating that version 2.0 of .Net is needed.
Better yet: Update to use a current .Net version.
Thank you!

.NET 2 required error on 2012 R2

What steps will reproduce the problem?
1. Install Microsoft Windows Server 2012 R2, e.g.:
a) Download 2012 R2 Trial:
   http://technet.microsoft.com/en-us/evalcenter/dn205286.aspx
   or
b) Start an Amazon EC2 Microsoft Windows Server 2012 R2 Micro Instance
   http://aws.amazon.com/windows/amis/
   http://aws.amazon.com/free/
2. Check .NET versions installed, e.g.:
   dir %WINDIR%\Microsoft.Net\Framework\v* /O:-N /B
   v4.0.30319
   v2.0.50727
   v1.1.4322
   v1.0.3705
3. Install Winhasher
https://code.google.com/p/winhasher/

What is the expected output? What do you see instead?
- Successful installation.
- Setup error:
  "The Microsoft .NET Framework version 2.0 or higher is required to run
   this application, but I couldn't find it installed on your system. Would
   you like to download it now?"

What version of the product are you using? On what operating system?
- Current Release 1.6.2.67.
- Windows Server 2012 R2 Standard Build 9600 (RTM)

Please provide any additional information below.
- Works great on Windows 7 Ultimate SP1 (64-bit).

Original issue reported on code.google.com by [email protected] on 12 Jun 2014 at 10:18

Attachments:

• [winhasher - NET 2 required - Jun 14.png](https://storage.googleapis.com/google-code-attachments/winhasher/issue-9/comment-0/winhasher - NET 2 required - Jun 14.png)

FEATURE REQUEST

What is the expected output? What do you see instead?
I want Winhasher be able to create and verify hash/checksum of cd/dvd/bluray 
discs

What version of the product are you using? On what operating system?
Winhasher ver. 1.6.0.43 on Windows XP SP3

Please provide any additional information below.
ALL of the open source hash/checksum verifiers do not have this feature.
-Thank you

Original issue reported on code.google.com by [email protected] on 14 Jul 2011 at 12:04

• Merged into: #1

Donations to "gpfjeff" ?

No problems !
Wanted to say thank you for WinHasher.
Best comparer :)
How can I make a donation ? I don't have crypto-currency, to old for that gig.

WinHasher is not listed in https://alternativeto.net/
I will be adding it in the next few days ... you deserve to be promoted.
A public thank you

Allow option to disable MD5 warning

I received the following request via e-mail:

"Your WinHasher is an excellent program but the warning message about MD5 is 
quite annoying and makes MD5WinHasher useless for me. If the warning was shown 
one time only it would be OK, but it is tiresome to see it time and again (when 
MD5 is chosen by default). I would appreciate it this message could be 
disabled."

The warning in question is a dialog that pops up when MD5 is selected from the 
Hash Algorithm drop-down list for the first time in a given session. This 
message is meant to remind users that MD5 is no longer considered secure and 
that they should being using stronger hashes such as SHA2. That said, if the 
user has MD5 selected when WinHasher is closed, the same dialog will be shown 
again when WinHasher opens. If the user uses MD5 regularly (likely because they 
must confirm a hash someone else has generated) and simply opens WinHasher to 
verify the file and then close it, this could admittedly get old pretty quickly.

One potential workaround for now would be to use the SendTo shortcuts, which 
are an option when WinHasher is installed. The user can right-click the file to 
open the context menu, select Send To, and pick the WinHasher MD5 shortcut. 
This shortcut does not generate the same warning as the main app, and even 
provides a place to allow the user to copy and paste the hash to compare the 
two values.

However, we should probably put in an option somewhere to disable the MD5 
warning as requested. It should be off by default so the warning should get 
displayed at least once, but the user should have the option of disabling it if 
they want. The hard part will be deciding *where* to put this option, as 
WinHasher doesn't currently have a separate settings panel. That will probably 
be the hardest part to get "right". Perhaps we should create a new Settings tab 
and move the "show tooltips" checkbox in there along with this option.

Original issue reported on code.google.com by [email protected] on 20 Feb 2014 at 6:49

SendTo links not working for "limited" (i.e. non-admin) accounts

I received the following e-mail report from a user:

"I am a limited user. When I install Winhasher, I run it as Windows 
Administrator and enter Admin password. However, then the in the limited 
account I always use, I do not see the 'send to' commands in windows explorer.

"To avoid this, when I install Winhasher to a computer, I have to give my 
limited account temporarly Admin power. This is not convenient I believe."

I haven't been able to follow up on this, but it sounds like the installer is 
setting up the SendTo links for the admin account but not for non-admin 
accounts. Either that, or it's forcing the user to run WinHasher as an admin 
user in order to get it to work. I don't know what operating system the user is 
operating under; the user wrote from a GMail account, so there are no clues in 
the message headers about the client OS. Presumably, he/she is using Windows 7 
or 8.

I'll try and run some tests on my non-development Windows 7 machine, which 
should have WinHasher installed in the same manner as a typical user would.

This may or may not be related to closed Issue 5.

Original issue reported on code.google.com by [email protected] on 19 Dec 2013 at 7:47

Feature Request

What steps will reproduce the problem?
N/A

What is the expected output? What do you see instead?
N/A

What version of the product are you using? On what operating system?
v1.6 from installer on Windows 7 x64

Please provide any additional information below.
I currently use two other hashing programs primarily to verify file integrity.  
I use hashtab, which is very easy to use and integrates uniquely with Windows 
and allows me to paste in a hash for comparison, and MD5Checker, which is 
capable of MD5 hashing many files in sequence and putting the results in a 
single or multiple files.  Both are available from Softpedia, which is nice 
that they certify they are 100% spyware free, but neither is open source, which 
I would prefer... The mass hashing functionality of MD5Checker is what I would 
like to see added to Winhasher.  The ability to hash many files at once and 
save the output to a single or multiple files is a must-have for me, and 
unfortunately my current program of choice only does MD5.

I frequently move files around the network at work, and it's nice to be able to 
verify them quickly and easily from a hash file I just move around with them, 
either an individual hash file for each, or in a single mass hash file.  I also 
often compile my own diagnostic and troubleshooting CDs, on which I will 
typically include a single file that contains a hash of every file on the disc 
so that it can be verified.  These discs go through a lot of swapping around, 
and so over time they take a beating and need to be verified and/or replaced.  
Ubuntu does something very similar with their CDs.  The root of the CD contains 
a hash of every file on it, therefore the OS disc can verify its own integrity. 
 I would like Winhasher to be able to do that as a 4th mode of operation so it 
can replace both programs.

Please note, three things are very important in the implementation of the mass 
hash files.  First, it needs to support both full and relative paths so they 
can be moved around without issue.  Secondly, it needs to maintain 
compatibility with the standard Linux command-line hashing utilities (such as 
md5sum) so that the hash files themselves are easily cross-platform.  And 
lastly, subfolder recursion is a must, so entire folder trees can be hashed 
easily.  I have attached sample hash files from MD5checker and an Ubuntu CD.  I 
would be glad to assist in testing or answer any questions you may have about 
my usage of the hash files.

Original issue reported on code.google.com by [email protected] on 18 Dec 2010 at 4:25

Attachments:

• MD5checker.md5
• ubuntu.md5