Wireshark-announce: [Wireshark-announce] Wireshark 1.12.8 is now available
From: Wireshark announcements <wireshark-announce@xxxxxxxxxxxxx>
Date: Wed, 14 Oct 2015 12:39:45 -0700
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I'm proud to announce the release of Wireshark 1.12.8. __________________________________________________________________ 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-2015-30 Pcapng file parser crash. Discovered by Dario Lombardo and Shannon Sabens. ([2]Bug 11455) [3]CVE-2015-7830 The following bugs have been fixed: * Last Address field for IPv6 RPL routing header is interpreted incorrectly. ([4]Bug 10560) * Comparing two capture files crashes Wireshark when navigating the results. ([5]Bug 11098) * 802.11 frame is not correctly dissected if it contains HT Control. ([6]Bug 11351) * GVCP bit-fields not updated. ([7]Bug 11442) * Tshark crash when specifying ssl.keys_list on CLI. ([8]Bug 11443) * pcapng: SPB capture length is incorrectly truncated if IDB snaplen = 0. ([9]Bug 11483) * pcapng: NRB IPv4 address is endian swapped but shouldn't be. ([10]Bug 11484) * pcapng: NRB with options causes file read failure. ([11]Bug 11485) * pcapng: ISB without if_drop option is shown as max value. ([12]Bug 11489) * UNISTIM dissector - Message length not included in offset for "Select Adjustable Rx Volume". ([13]Bug 11497) 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 DIAMETER, GVCP, IEEE 802.11, IPv6, and UNISTIM New and Updated Capture File Support pcapng __________________________________________________________________ Getting Wireshark Wireshark source code and installation packages are available from [14]https://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 [15]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. ([16]Bug 1419) The BER dissector might infinitely loop. ([17]Bug 1516) Capture filters aren't applied when capturing from named pipes. ([18]Bug 1814) Filtering tshark captures with read filters (-R) no longer works. ([19]Bug 2234) The 64-bit Windows installer does not support Kerberos decryption. ([20]Win64 development page) Resolving ([21]Bug 9044) reopens ([22]Bug 3528) so that Wireshark no longer automatically decodes gzip data when following a TCP stream. Application crash when changing real-time option. ([23]Bug 4035) Hex pane display issue after startup. ([24]Bug 4056) Packet list rows are oversized. ([25]Bug 4357) Wireshark and TShark will display incorrect delta times in some cases. ([26]Bug 4985) __________________________________________________________________ Getting Help Community support is available on [27]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 [28]the web site. Official Wireshark training and certification are available from [29]Wireshark University. __________________________________________________________________ Frequently Asked Questions A complete FAQ is available on the [30]Wireshark web site. __________________________________________________________________ Last updated 2015-10-14 11:35:09 PDT References 1. https://www.wireshark.org/security/wnpa-sec-2015-30.html 2. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=11455 3. http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-7830 4. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=10560 5. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=11098 6. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=11351 7. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=11442 8. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=11443 9. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=11483 10. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=11484 11. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=11485 12. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=11489 13. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=11497 14. https://www.wireshark.org/download.html 15. https://www.wireshark.org/download.html#thirdparty 16. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=1419 17. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=1516 18. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=1814 19. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=2234 20. https://wiki.wireshark.org/Development/Win64 21. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=9044 22. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=3528 23. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=4035 24. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=4056 25. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=4357 26. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=4985 27. https://ask.wireshark.org/ 28. https://www.wireshark.org/lists/ 29. http://www.wiresharktraining.com/ 30. https://www.wireshark.org/faq.html Digests wireshark-1.12.8.tar.bz2: 29216939 bytes MD5(wireshark-1.12.8.tar.bz2)=988a4595a4a87dafb3c4870ea40e89b5 SHA1(wireshark-1.12.8.tar.bz2)=d8c23120525a2f3505e822b7684e7367bcd0ba70 RIPEMD160(wireshark-1.12.8.tar.bz2)=bf87fd1e3404d04f6123d09798b46ea5b2af49e9 Wireshark-win64-1.12.8.exe: 29873720 bytes MD5(Wireshark-win64-1.12.8.exe)=c84ebbac5e745baa9ac111d65b2bfa47 SHA1(Wireshark-win64-1.12.8.exe)=390007f3a8b9272b02ec0e582363c80e9b7f2a3b RIPEMD160(Wireshark-win64-1.12.8.exe)=4fa29aa0059770ec92b72b2e5ba6d1f5646d74e9 Wireshark-win32-1.12.8.exe: 23626472 bytes MD5(Wireshark-win32-1.12.8.exe)=4ce67178ca615d20fc4df6969e8c8358 SHA1(Wireshark-win32-1.12.8.exe)=f29629affdf09643c0dec192c4a666e599052263 RIPEMD160(Wireshark-win32-1.12.8.exe)=938ee624703f23b4af7fefa466665f957ba7389c WiresharkPortable-1.12.8.paf.exe: 29925920 bytes MD5(WiresharkPortable-1.12.8.paf.exe)=fd32d16cdd9f5c4df966a5ebabe38581 SHA1(WiresharkPortable-1.12.8.paf.exe)=98719b8b6ce699ec1dbe8267a844a3972f32f33b RIPEMD160(WiresharkPortable-1.12.8.paf.exe)=bb08ee9f16d5da3cb105bf99656307bad6a42381 Wireshark 1.12.8 Intel 64.dmg: 26464983 bytes MD5(Wireshark 1.12.8 Intel 64.dmg)=c80a98b5d8f22bda5c563e4d404f0f7c SHA1(Wireshark 1.12.8 Intel 64.dmg)=11449cb460a1272de7deaa9d65e97159835753fc RIPEMD160(Wireshark 1.12.8 Intel 64.dmg)=70f353c5b54fa704508916a114d06d53c5aa1349 Wireshark 1.12.8 Intel 32.dmg: 21918844 bytes MD5(Wireshark 1.12.8 Intel 32.dmg)=0bc58a80dc827ff2b84c24b04334e8e7 SHA1(Wireshark 1.12.8 Intel 32.dmg)=48ef32167f4705bfef4cae969fe407a69afa27ac RIPEMD160(Wireshark 1.12.8 Intel 32.dmg)=c05e586f2ff6a966eceaccb4db68c6c5bfefb9e0 patch-wireshark-1.12.7-to-1.12.8.bz2: 441533 bytes MD5(patch-wireshark-1.12.7-to-1.12.8.bz2)=0346dea0f19d86f67ecc38f0bb3f0906 SHA1(patch-wireshark-1.12.7-to-1.12.8.bz2)=c4abf43357e1a1686c80cba2109e82c1f8a5ae08 RIPEMD160(patch-wireshark-1.12.7-to-1.12.8.bz2)=021f138a52ba6c430d9bedd906423a69a084102e -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEARECAAYFAlYer4EACgkQpw8IXSHylJrZkACeIedjgjnWAxiveVNTYRh1i+Ky XVgAn3iJJdfjIIMAtELVikTj3jy40RMi =gQ16 -----END PGP SIGNATURE-----
- Next by Date: [Wireshark-announce] Wireshark 2.0.0rc1 is now available
- Next by thread: [Wireshark-announce] Wireshark 2.0.0rc1 is now available
- Index(es):