Wireshark-users: [Wireshark-users] Wireshark 2.4.1 is now available
From: Gerald Combs <gerald@xxxxxxxxxxxxx>
Date: Tue, 29 Aug 2017 12:28:39 -0700
I'm proud to announce the release of Wireshark 2.4.1.
__________________________________________________________________
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 bugs have been fixed:
* [1]wnpa-sec-2017-38
MSDP dissector infinite loop ([2]Bug 13933)
* [3]wnpa-sec-2017-39
Profinet I/O buffer overrun ([4]Bug 13847)
* [5]wnpa-sec-2017-40
Modbus dissector crash ([6]Bug 13925)
* [7]wnpa-sec-2017-41
IrCOMM dissector buffer overrun ([8]Bug 13929)
* Incorrect presentation of Ascend-Data-Filter (RADIUS attribute
242). ([9]Bug 11630)
* Confusing "Apply a display filter <Command/>" keyboard shortcut.
([10]Bug 12450)
* Wireshark crashes at startup if it needs to display a dialog early
in the startup process. ([11]Bug 13275)
* RADIUS dictionary: BEGIN-VENDOR does not support
format=Extended-Vendor-Specific-\*. ([12]Bug 13745)
* Dumpcap on big-endian machines writes out corrupt, unreadable
Enhanced Packet Blocks. ([13]Bug 13802)
* Interface Toolbar support for Windows. ([14]Bug 13833)
* Wireshark should behave better on high resolution displays on
Windows. ([15]Bug 13877)
* Udpdump.pod missing from build. ([16]Bug 13903)
* RTP Player Format Error. ([17]Bug 13906)
* VNC Protocol disector : Framebuffer Updates. ([18]Bug 13910)
* DNS LOC RRs with out-of-range longitude or latitude aren't shown as
errors. ([19]Bug 13914)
* DIS Dissector Entity Appearance Record displayed in wrong location.
([20]Bug 13917)
* Win64 CMake bug - (CYGWIN_INSTALL_PATH redefinition) causing
missing packages when using CMake 3.9.0. ([21]Bug 13922)
* APL records parsed incorrectly for IPv4 prefixes. ([22]Bug 13923)
* File->Merge dialog doesn't show all options. Resizing doesn't help.
([23]Bug 13924)
* TCAP SRT Analysis incorrectly matched TCAP begins and ends.
([24]Bug 13926)
* Error in MKA Distributed SAK parameter set dissection. ([25]Bug
13927)
* E.212: Check length before trying 3-digits MNC. ([26]Bug 13935)
* mpeg_descriptor: AC3 System A: Respect descriptor length. ([27]Bug
13939)
* Crash in Wireshark using Dumper:dump() from Lua. ([28]Bug 13944)
* MRCPv2 not decoded correctly. ([29]Bug 13952)
* UDP Checksum verification not working for 0x0000 checksum. ([30]Bug
13955)
* OSPF v3 LSA Type not well parsed. ([31]Bug 13979)
* GTPv2 - decoding issue for Packet Flow ID (type 123). ([32]Bug
13987)
* TRANSUM fails to calculate RTE figures for DCE-RPC where request
Packet Type is zero. ([33]Bug 13988)
* BTLE Hop and SCA fields incorrectly dissected in BLE CONNECT_REQ.
([34]Bug 13990)
* [oss-fuzz] BGP memleak: ASAN: 276 byte(s) leaked in 5
allocation(s). ([35]Bug 13995)
* Some Infiniband Connect Req fields are not decoded correctly.
([36]Bug 13997)
* GTP: gtp.ext_comm_flags_II_pmtsmi bit not decoded correctly.
([37]Bug 14001)
* InfiniBand: sIP and dIP inside IP CM Private Data are decoded in
the wrong order. ([38]Bug 14002)
* 802.11 wlan.ft.subelem.r0kh_id should be sequence of bytes.
([39]Bug 14004)
* USB capture: Unrecognized libpcap format or not libpcap data.
([40]Bug 14006)
* SQ Header Pointer in NVMoF response capsule is decoded with the
wrong endian. ([41]Bug 14008)
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
BGP, BT LE, DIS, DNS, E.212, EPL, GTP, GTPv2, IEEE 802.11, InfiniBand,
IPv4, IrCOMM, MKA, Modbus, MPEG Descriptor, MRCPv2, MSDP, MTP2, Nordic
BLE, NVMe, OSPF, pcapng MIME, PMIPv6, Profinet I/O, RADIUS, SML, TCAP,
TRANSUM, UA3G, UDP, VNC, and ZigBee
New and Updated Capture File Support
There is no new or updated capture file support in this release.
__________________________________________________________________
Getting Wireshark
Wireshark source code and installation packages are available from
[42]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 [43]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. ([44]Bug 1419)
The BER dissector might infinitely loop. ([45]Bug 1516)
Capture filters aren't applied when capturing from named pipes.
([46]Bug 1814)
Filtering tshark captures with read filters (-R) no longer works.
([47]Bug 2234)
Application crash when changing real-time option. ([48]Bug 4035)
Wireshark and TShark will display incorrect delta times in some cases.
([49]Bug 4985)
Wireshark should let you work with multiple capture files. ([50]Bug
10488)
__________________________________________________________________
Getting Help
Community support is available on [51]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 [52]the web site.
Official Wireshark training and certification are available from
[53]Wireshark University.
__________________________________________________________________
Frequently Asked Questions
A complete FAQ is available on the [54]Wireshark web site.
__________________________________________________________________
Last updated 2017-08-29 18:55:42 UTC
References
1. https://www.wireshark.org/security/wnpa-sec-2017-38.html
2. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=13933
3. https://www.wireshark.org/security/wnpa-sec-2017-39.html
4. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=13847
5. https://www.wireshark.org/security/wnpa-sec-2017-40.html
6. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=13925
7. https://www.wireshark.org/security/wnpa-sec-2017-41.html
8. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=13929
9. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=11630
10. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=12450
11. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=13275
12. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=13745
13. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=13802
14. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=13833
15. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=13877
16. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=13903
17. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=13906
18. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=13910
19. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=13914
20. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=13917
21. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=13922
22. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=13923
23. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=13924
24. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=13926
25. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=13927
26. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=13935
27. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=13939
28. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=13944
29. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=13952
30. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=13955
31. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=13979
32. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=13987
33. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=13988
34. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=13990
35. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=13995
36. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=13997
37. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14001
38. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14002
39. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14004
40. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14006
41. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14008
42. https://www.wireshark.org/download.html
43. https://www.wireshark.org/download.html#thirdparty
44. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=1419
45. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=1516
46. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=1814
47. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=2234
48. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=4035
49. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=4985
50. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=10488
51. https://ask.wireshark.org/
52. https://www.wireshark.org/lists/
53. http://www.wiresharktraining.com/
54. https://www.wireshark.org/faq.html
Digests
wireshark-2.4.1.tar.xz: 28780384 bytes
SHA256(wireshark-2.4.1.tar.xz)=02ddbcf9b10f9dfa1e36eec00fe00cb5b5ce8e07203843baf056ac7909911fcd
RIPEMD160(wireshark-2.4.1.tar.xz)=4e47f79741fe09ed404e03ab51be617abc3ae3d5
SHA1(wireshark-2.4.1.tar.xz)=2a52aeefba0a45747b1e4593c82c6efc33aa4182
MD5(wireshark-2.4.1.tar.xz)=22b925108e0b65d6560f0af161157266
Wireshark-win32-2.4.1.exe: 53597448 bytes
SHA256(Wireshark-win32-2.4.1.exe)=8a2be35c125010538692130af6fc4f9384e3a3caa4f49eec7fc17e238512c067
RIPEMD160(Wireshark-win32-2.4.1.exe)=a9c9567857ca768835ed9ab040a2ae1b86df779f
SHA1(Wireshark-win32-2.4.1.exe)=392c5eebe1aef355e6e660e34cb98ad2dde5e2b2
MD5(Wireshark-win32-2.4.1.exe)=f7daa36cdd469bf067e258c9d1847ee6
Wireshark-win64-2.4.1.exe: 59132608 bytes
SHA256(Wireshark-win64-2.4.1.exe)=c97d6a43bca6e706975b45bfa99d320674003673f8bc8337954694ef14e6cc26
RIPEMD160(Wireshark-win64-2.4.1.exe)=70efd612db44caa65f40946557891fd952445a4e
SHA1(Wireshark-win64-2.4.1.exe)=0ccf8188aa3970adea3003c0e7bff12cd6d34313
MD5(Wireshark-win64-2.4.1.exe)=2e71aed667c5a6de9acced176a504939
Wireshark-win32-2.4.1.msi: 43048960 bytes
SHA256(Wireshark-win32-2.4.1.msi)=467f29e274fa6da0072295198217ba324db7885d49f1d6e6e40008622ffe3ea0
RIPEMD160(Wireshark-win32-2.4.1.msi)=16832d856347c305c14403e65c79f10c7961affd
SHA1(Wireshark-win32-2.4.1.msi)=a04faea8ee31bbd621719605c95ade9536aebab6
MD5(Wireshark-win32-2.4.1.msi)=9000a088689fcd24253d363a853bb7aa
Wireshark-win64-2.4.1.msi: 48398336 bytes
SHA256(Wireshark-win64-2.4.1.msi)=7a75a2eebfa197dd34c17707ddf6065921b24af58470fa85d44498402866db1c
RIPEMD160(Wireshark-win64-2.4.1.msi)=13ae3e3cace6968af1507d26d5b0224f3a5c427c
SHA1(Wireshark-win64-2.4.1.msi)=5f533bf7e6226ebb9d59f0cef149015869364e69
MD5(Wireshark-win64-2.4.1.msi)=cfb3b9fe4b73e4cb6d5bfc0b37b7d841
WiresharkPortable_2.4.1.paf.exe: 46309696 bytes
SHA256(WiresharkPortable_2.4.1.paf.exe)=f75753a335cb6278527c21822c07a08a3ca977c83da23c7fc80c7bbdf3fabcce
RIPEMD160(WiresharkPortable_2.4.1.paf.exe)=953ed214dc32d07fa5891ec8738180a21b95a0d2
SHA1(WiresharkPortable_2.4.1.paf.exe)=3ac54e3129c82c919c8c00fd5ce28cd8d8230297
MD5(WiresharkPortable_2.4.1.paf.exe)=bee21315ce99ecfff83f61d950be8d46
Wireshark 2.4.1 Intel 64.dmg: 35197766 bytes
SHA256(Wireshark 2.4.1 Intel
64.dmg)=cbf1f66020d049e645edd9ee8f0ebdd7d71d019d3fb2c44e028fcd65195b268b
RIPEMD160(Wireshark 2.4.1 Intel
64.dmg)=37c33371a0b142fea753f3723f6a30f7476fea18
SHA1(Wireshark 2.4.1 Intel 64.dmg)=d841c155e6aa8681cefdaffec4b95432de865957
MD5(Wireshark 2.4.1 Intel 64.dmg)=911497d6ea05821321a824bae57d7835
Attachment:
signature.asc
Description: OpenPGP digital signature
- Prev by Date: Re: [Wireshark-users] Fw: Re: How to find the bottleneck?
- Next by Date: [Wireshark-users] Wireshark 2.2.9 is now available
- Previous by thread: Re: [Wireshark-users] Fw: Re: How to find the bottleneck?
- Next by thread: [Wireshark-users] Wireshark 2.2.9 is now available
- Index(es):