-
It's the PNG/Mpeg-2/ but that is different than the Ethernet version, but the wikipedia entry I believe is wrong to list the 802.3 along side the png/mp2/zip crc32...
It seems to also be known as crc32b, the tables they use are different, php source code has the differences in php-5.2.11\ext\hash\php_hash_crc32_tables.h
The php crc32b seems to give the same results that I've come to expect...
2009-11-03 17:02:20 UTC by richrumble
-
Which version of CRC32 are you looking for? There are several! See http://en.wikipedia.org/wiki/Cyclic_redundancy_check for a list.
2009-11-03 14:57:14 UTC by jessekornblum
-
Were looking to utilize hashdeep/md5deep in our File Integrity Monitor, would it be possible to add crc32 hash's? We've noticed that we can scan for changes much faster using programs that use crc32 hash's, and we can work out possible hash collisions using other algo's (md5/sha) when duplicate crc32 hash's are detected. I think crc32 could greatly speed up searching for file changes when...
2009-11-02 17:26:28 UTC by richrumble
-
I created MD5 sums in Piecewise mode how to check inegrity of those files?.
2009-10-07 23:22:14 UTC by kamikazeepl
-
The fix checked into SVN has passed testing and is accepted.
2009-09-29 12:55:44 UTC by jessekornblum
-
It would occasionally be useful to have a progressive mode where a file is hashed from the beginning to a series of ending offsets incremented by blocks.
For example, forensic drive images are often hashed using MD5. When copied to a larger working drive in 1-to-1 mode, the hash can only be verified if you know the number of sectors in the original drive. Using progressive mode, hashes for...
2009-09-25 16:23:32 UTC by petiepooo
-
It works under my test environment. And the last block is omitted as you intended.
I've been holding off on the progressive patch until you checked this into SVN. I had to rework it a bit, but will submit shortly.
Thanks.
2009-09-25 16:06:10 UTC by petiepooo
-
petiepooo, can you please test out the 'fixed' version now in SVN? (I put fixed in quotes as it's certainly possible that the current version has bugs..) [grin] thanks!
2009-09-24 10:38:10 UTC by jessekornblum
-
After thinking more about the issue, I've added a 'last block' check that avoids printing out a hash if no data was read in the block (e.g. bytes 512-511 in your example). Whether the C style offset or Python style offset is more intuitive is a toss-up. Regardless, users must learn *some* programming language's style. As such I'm sticking with the one they can use in a hex editor.
2009-09-24 10:36:50 UTC by jessekornblum
-
jessekornblum committed revision 206 to the md5deep SVN repository, changing 3 files.
2009-09-24 10:35:52 UTC by jessekornblum