Wireshark-users: [Wireshark-users] Wireshark 2.2.11 file hash update
Date Index · Thread Index · Other Months · All Mailing Lists
Date Prev · Date Next · Thread Prev · Thread Next
From: Gerald Combs <gerald@xxxxxxxxxxxxx>
Date: Thu, 30 Nov 2017 15:08:25 -0800
Earlier today Wireshark 2.4.3 was released. The announcement included the following file hashes, which are incorrect:

> wireshark-2.2.11.tar.bz2: 32379934 bytes
> SHA256(wireshark-2.2.11.tar.bz2)=f8a5a13ce27dfab0c64a49273c6c8d0550c57b066fa4c2c6909119bb2a07a702
> RIPEMD160(wireshark-2.2.11.tar.bz2)=3575d108ef626fcfc8121d779d70f3f235843f4e
> SHA1(wireshark-2.2.11.tar.bz2)=a24f0badbe3bab28e3c2553e15f82af3470ccff5
> 
> Wireshark-win32-2.2.11.exe: 44651304 bytes
> SHA256(Wireshark-win32-2.2.11.exe)=ee3da6f110b31ed2ec4a4a0aea90cd4c9bea95fa1c674e98c75c98a0bdfbdfe2
> RIPEMD160(Wireshark-win32-2.2.11.exe)=2f10a82c05408ae7b66e49276bb58120e98fc513
> SHA1(Wireshark-win32-2.2.11.exe)=f33e585f7def34b50aa55de6886c3b872e17ea0d
> 
> Wireshark-win64-2.2.11.exe: 56153456 bytes
> SHA256(Wireshark-win64-2.2.11.exe)=063cc3370df4a2c84f122d8933dd39bb711af1075dd8c2a4ab2457e83a92997f
> RIPEMD160(Wireshark-win64-2.2.11.exe)=c2432253736230ad8104dd546949e662297f64a5
> SHA1(Wireshark-win64-2.2.11.exe)=89e01c194da4d9783951db3cd3d3fef2401881f0
> 
> WiresharkPortable_2.2.11.paf.exe: 46262768 bytes
> SHA256(WiresharkPortable_2.2.11.paf.exe)=dc20c41ab1f5a1e432a9b11f1dcefc7d9c161ac507aab95cb8391cc8194e77d2
> RIPEMD160(WiresharkPortable_2.2.11.paf.exe)=ff45f9a1c30a5632d8544f96120881ea5d286f94
> SHA1(WiresharkPortable_2.2.11.paf.exe)=2235b4a9db4e02a9ecc411aef4ce3edf973a789d
> 
> Wireshark 2.2.11 Intel 64.dmg: 33510131 bytes
> SHA256(Wireshark 2.2.11 Intel 64.dmg)=36c97cf2c765184220545948dad5a72b06a8dabc93d54cef6c5cfdb62e49cac1
> RIPEMD160(Wireshark 2.2.11 Intel 64.dmg)=5245fa8d411b631467d1064a35605a13b28172ea
> SHA1(Wireshark 2.2.11 Intel 64.dmg)=9615346813b27a88d02a76bbd57341d7e37aeb2e

The correct file hashes are as follows:

wireshark-2.2.11.tar.bz2: 32379934 bytes
SHA256(wireshark-2.2.11.tar.bz2)=a9f11621e85d7e1d72259157edd94825e72af3fd72e184b8474459f92ad5fc40
RIPEMD160(wireshark-2.2.11.tar.bz2)=a14ac4bae54003f286634f95131007fa6cbbaced
SHA1(wireshark-2.2.11.tar.bz2)=24f2d70684d8fa9ffb5f38924ce34be338c5098a

Wireshark-win32-2.2.11.exe: 44651304 bytes
SHA256(Wireshark-win32-2.2.11.exe)=975ed54f6b1ed34236f2f0439de8641177628b87a2ac3148a2e8c1e199535940
RIPEMD160(Wireshark-win32-2.2.11.exe)=4c91ccb64e7c859b393ac4a310285ea6d93bf89f
SHA1(Wireshark-win32-2.2.11.exe)=2e2eb498301d941990a9667f7f044f3e97e30f8f

Wireshark-win64-2.2.11.exe: 56153456 bytes
SHA256(Wireshark-win64-2.2.11.exe)=7642a6ef1e965a7264512851b42dcadc7cbe7620a2fbeb8b072118d77b93a955
RIPEMD160(Wireshark-win64-2.2.11.exe)=6934a0c400a82c410bb6878018c45d2255d9669d
SHA1(Wireshark-win64-2.2.11.exe)=1103fecbe07413c4b707ffbd398f4997a9accc4a

WiresharkPortable_2.2.11.paf.exe: 46262768 bytes
SHA256(WiresharkPortable_2.2.11.paf.exe)=860bec6a0b941bc6710baa39b7c01da817d779eb3d9835dbc17310a9e0cb3049
RIPEMD160(WiresharkPortable_2.2.11.paf.exe)=0ab67eb682eebdd96cd631278a3c76cb1c913484
SHA1(WiresharkPortable_2.2.11.paf.exe)=cf90288da8d6e856ba12dc305cf0c76d40571634

Wireshark 2.2.11 Intel 64.dmg: 33510131 bytes
SHA256(Wireshark 2.2.11 Intel 64.dmg)=a37e7395f3e5bd69fee972fb51183b7dceb939e2812d88e8c0c543a84150cdae
RIPEMD160(Wireshark 2.2.11 Intel 64.dmg)=2b51ae4d076ad317fc14f1ff3b958f8ebfb8b6ad
SHA1(Wireshark 2.2.11 Intel 64.dmg)=49b3d5dafd1e6b58563a7d98ea020a2f81970a1d

My apologies for any inconvenience.

Attachment: signature.asc
Description: OpenPGP digital signature