Wireshark-users: [Wireshark-users] Wireshark 1.10.9 is now available
From: Gerald Combs <gerald@xxxxxxxxxxxxx>
Date: Thu, 31 Jul 2014 14:51:39 -0700
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I'm proud to announce the release of Wireshark 1.10.9. __________________________________________________________ What is Wireshark? Wireshark is the world's most popular network protocol analyzer. It is used for troubleshooting, analysis, development and education. __________________________________________________________ What's New Bug Fixes The following vulnerabilities have been fixed. * [1]wnpa-sec-2014-08 The Catapult DCT2000 and IrDA dissectors could underrun a buffer. Versions affected: 1.10.0 to 1.10.8 * [2]wnpa-sec-2014-09 The GSM Management dissector could crash. ([3]Bug 10216) Versions affected: 1.10.0 to 1.10.8 * [4]wnpa-sec-2014-10 The RLC dissector could crash. ([5]Bug 9795) Versions affected: 1.10.0 to 1.10.8 * [6]wnpa-sec-2014-11 The ASN.1 BER dissector could crash. ([7]Bug 10187) Versions affected: 1.10.0 to 1.10.8 The following bugs have been fixed: * GSM MAP: ensure that p2p_dir is always initialized before calling GSM SMS dissector ([8]Bug 10234) * BFCP: include padding length in calculation of correct attribute length ([9]Bug 10240) * GTP: allow empty Data Record Packet IE ([10]Bug 10277) * WebSocket: increase max unmask payload size to 256K and indicate that packet is truncated is going above the new limit ([11]Bug 10283) New and Updated Features There are no new features in this release. New Protocol Support There are no new protocols in this release. Updated Protocol Support New and Updated Capture File Support __________________________________________________________ Getting Wireshark Wireshark source code and installation packages are available from [12]http://www.wireshark.org/download.html. Vendor-supplied Packages Most Linux and Unix vendors supply their own Wireshark packages. You can usually install or upgrade Wireshark using the package management system specific to that platform. A list of third-party packages can be found on the [13]download page on the Wireshark web site. __________________________________________________________ File Locations Wireshark and TShark look in several different locations for preference files, plugins, SNMP MIBS, and RADIUS dictionaries. These locations vary from platform to platform. You can use About->Folders to find the default locations on your system. __________________________________________________________ Known Problems Dumpcap might not quit if Wireshark or TShark crashes. ([14]Bug 1419) The BER dissector might infinitely loop. ([15]Bug 1516) Capture filters aren't applied when capturing from named pipes. ([16]Bug 1814) Filtering tshark captures with read filters (-R) no longer works. ([17]Bug 2234) The 64-bit Windows installer does not support Kerberos decryption. ([18]Win64 development page) Resolving ([19]Bug 9044) reopens ([20]Bug 3528) so that Wireshark no longer automatically decodes gzip data when following a TCP stream. Application crash when changing real-time option. ([21]Bug 4035) Hex pane display issue after startup. ([22]Bug 4056) Packet list rows are oversized. ([23]Bug 4357) Summary pane selected frame highlighting not maintained. ([24]Bug 4445) Wireshark and TShark will display incorrect delta times in some cases. ([25]Bug 4985) __________________________________________________________ Getting Help Community support is available on [26]Wireshark's Q&A site and on the wireshark-users mailing list. Subscription information and archives for all of Wireshark's mailing lists can be found on [27]the web site. Official Wireshark training and certification are available from [28]Wireshark University. __________________________________________________________ Frequently Asked Questions A complete FAQ is available on the [29]Wireshark web site. __________________________________________________________ Last updated 2014-07-31 12:02:43 PDT References 1. https://www.wireshark.org/security/wnpa-sec-2014-08.html 2. https://www.wireshark.org/security/wnpa-sec-2014-09.html 3. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=10216 4. https://www.wireshark.org/security/wnpa-sec-2014-10.html 5. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=9795 6. https://www.wireshark.org/security/wnpa-sec-2014-11.html 7. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=10187 8. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=10234 9. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=10240 10. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=10277 11. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=10283 12. http://www.wireshark.org/download.html 13. http://www.wireshark.org/download.html#thirdparty 14. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=1419 15. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=1516 16. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=1814 17. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=2234 18. https://wiki.wireshark.org/Development/Win64 19. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=9044 20. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=3528 21. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=4035 22. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=4056 23. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=4357 24. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=4445 25. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=4985 26. http://ask.wireshark.org/ 27. http://www.wireshark.org/lists/ 28. http://www.wiresharktraining.com/ 29. http://www.wireshark.org/faq.html Digests wireshark-1.10.9.tar.bz2: 26769965 bytes MD5(wireshark-1.10.9.tar.bz2)=c8f0bf0f5bff39ae4ad0a48e41585cd2 SHA1(wireshark-1.10.9.tar.bz2)=902b0eb6f3e007c9ffcf6f76c02403bd90319f96 RIPEMD160(wireshark-1.10.9.tar.bz2)=4517b2e98cf41a00ff617a31c79626285d6722f2 Wireshark-win32-1.10.9.exe: 22166304 bytes MD5(Wireshark-win32-1.10.9.exe)=fcfb3abc085b2d31bec470ddcd0dc2b4 SHA1(Wireshark-win32-1.10.9.exe)=0d0e9c4af512029b61bc160783d34a41a21863f6 RIPEMD160(Wireshark-win32-1.10.9.exe)=9bbd2d443901e17472ac4d2b4d5918e226175e5d Wireshark-win64-1.10.9.exe: 28016536 bytes MD5(Wireshark-win64-1.10.9.exe)=975a95308570873bb71f1663c4706fcd SHA1(Wireshark-win64-1.10.9.exe)=848b7ea90f398c005a9d1986dbaa9be47476a4a6 RIPEMD160(Wireshark-win64-1.10.9.exe)=c9bc0f52eab4c9e90dfb493ce0e7d8a87fe8f509 Wireshark-1.10.9.u3p: 30653536 bytes MD5(Wireshark-1.10.9.u3p)=4074efd56c5757535f9dfaa7f74d9526 SHA1(Wireshark-1.10.9.u3p)=c298e23248a3b58b6ecdd7dbb2532969e9fbf293 RIPEMD160(Wireshark-1.10.9.u3p)=8bda60a20959e9f437d6855ec1c73a6744f21af4 WiresharkPortable-1.10.9.paf.exe: 23537080 bytes MD5(WiresharkPortable-1.10.9.paf.exe)=6f5e168cf2f1ca8ab8740b06fd12ebfd SHA1(WiresharkPortable-1.10.9.paf.exe)=5d8c131b138b4d8eeefc26788e5a57191ac89d97 RIPEMD160(WiresharkPortable-1.10.9.paf.exe)=2772a6e75cc0aba1c2a015b08226cc18bae46038 Wireshark 1.10.9 Intel 32.dmg: 20461818 bytes MD5(Wireshark 1.10.9 Intel 32.dmg)=e44028439e7ad12b2d1f015203d520cf SHA1(Wireshark 1.10.9 Intel 32.dmg)=467b18c9b000dd9bec4534d54afc3c1804ee54c2 RIPEMD160(Wireshark 1.10.9 Intel 32.dmg)=ee9045341aa810f32b588ece0598e2e26ce1d640 Wireshark 1.10.9 Intel 64.dmg: 24787099 bytes MD5(Wireshark 1.10.9 Intel 64.dmg)=f84f2aaef059241705e4456bc15e968e SHA1(Wireshark 1.10.9 Intel 64.dmg)=8d0e89971d5ae4bc909cdd5f2b6c17972008d2e3 RIPEMD160(Wireshark 1.10.9 Intel 64.dmg)=20e4526b0865f38a114da8451351144d01d394e8 patch-wireshark-1.10.8-to-1.10.9.bz2: 189834 bytes MD5(patch-wireshark-1.10.8-to-1.10.9.bz2)=8ad5f6a31dbc4484182f9403cc2abab1 SHA1(patch-wireshark-1.10.8-to-1.10.9.bz2)=65b680175698eb15e8904847f2e81d613c655453 RIPEMD160(patch-wireshark-1.10.8-to-1.10.9.bz2)=586b624493e329aad35152fedad739fe051f5bd4 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.14 (Darwin) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iEYEARECAAYFAlPaumsACgkQpw8IXSHylJocTwCfUkTaoAejITGvGVzPpqrvmQsK n/UAoL5GEzRiFdu6XO5o/VuXgoojHekJ =OUmw -----END PGP SIGNATURE-----
- Prev by Date: [Wireshark-users] Wireshark 1.12.0 is now available
- Previous by thread: [Wireshark-users] Wireshark 1.12.0 is now available
- Index(es):