01-19-2012, 08:16 PM
After a lot of testing this is either a text encoding problem or a logic mismatch in SHA1 algorithm implementations between Windows and Linux.
For a windows OS the strings I've posted are valid and confirmed by many other applications I've downloaded and tested using SHA1.
I hope its just a text encoding issue but I'm not certain of how or if its even possible to map the windows Windows-1252 text encoding to match the Linux encoding that this program can digest. I looped through every single encoding on Windows 7, roughly 80 different ones, and none of them remotely matched the strings that are being generated on your linux/unix boxes for the value '12345'.
Linux - 8cb2237d0679ca88db6464eac60da96345513964
Windows 7 (UTF8) - 1cba6360d8b03617fb7b33443596691b6e90006c
Windows 7 (UTF16) - 40e5cdd056f635757c9df10b27d0e12ffd30c4db
For a windows OS the strings I've posted are valid and confirmed by many other applications I've downloaded and tested using SHA1.
I hope its just a text encoding issue but I'm not certain of how or if its even possible to map the windows Windows-1252 text encoding to match the Linux encoding that this program can digest. I looped through every single encoding on Windows 7, roughly 80 different ones, and none of them remotely matched the strings that are being generated on your linux/unix boxes for the value '12345'.
Linux - 8cb2237d0679ca88db6464eac60da96345513964
Windows 7 (UTF8) - 1cba6360d8b03617fb7b33443596691b6e90006c
Windows 7 (UTF16) - 40e5cdd056f635757c9df10b27d0e12ffd30c4db