Wireshark-users: Re: [Wireshark-users] Dumpcap batch file front-end with event notification and t
Date Index · Thread Index · Other Months · All Mailing Lists
Date Prev · Date Next · Thread Prev · Thread Next
From: Christopher Maynard <Christopher.Maynard@xxxxxxxxx>
Date: Sat, 31 May 2014 19:30:48 +0000 (UTC)
Maynard, Chris <Christopher.Maynard@...> writes:

> Digests:
> dumpcap.txt: 102,998 bytes
> MD5(dumpcap.txt)= 2ee016a55e545b43082e63c611c7aad7
> SHA1(dumpcap.txt)= 7cb14aff6f9a48803a5a46ff9de4fdb408720283
> RIPEMD160(dumpcap.txt)= 9481bb71da59f72a7cdae506b79c2ae861009205

Well, apparently that wasn't the best method of distributing the batch file
since the mailers decided to make changes when they mangled the e-mail
addresses and stuck an extra semi-colon on the end of line 371 of the batch
file:

371c371
<         START "" "http://www.wireshark.org/docs/man-pages/dumpcap.html";
---
>         START "" "http://www.wireshark.org/docs/man-pages/dumpcap.html";;


So, if you copy/paste the 2,899 lines of text comprising the batch file from
http://www.wireshark.org/lists/wireshark-users/201405/msg00030.html, the
digests you should get are:

MD5(dumpcap.txt)= 513e5fe73f4ac0329c47eb2bc26cbfb2
SHA1(dumpcap.txt)= 9a870dd5633742666a48385dd7b39fb533352a40
RIPEMD160(dumpcap.txt)= 300523c206c545c371a6ff855d526e3ad02f2600

... and if you remove the semicolon from the end of line 371 that was
somehow added, you should then get the following digests:

MD5(dumpcap.txt)= 613e17ea07dcbdd58d35e6c84bb95fa1
SHA1(dumpcap.txt)= 508c4f686604c7669c21eaf9428755c765be8856
RIPEMD160(dumpcap.txt)= 2f3d59a4cac14a8e49e56171c49d046faf1a6d96

- Chris