Wireshark-dev: [Wireshark-dev] Wireshark 2.2.4 is now available
From: Gerald Combs <gerald@xxxxxxxxxxxxx>
Date: Mon, 23 Jan 2017 14:54:36 -0800
I'm proud to announce the release of Wireshark 2.2.4.
__________________________________________________________________
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-2017-01
The ASTERIX dissector could go into an infinite loop. ([2]Bug
13344)
* [3]wnpa-sec-2017-02
The DHCPv6 dissector could go into a large loop. ([4]Bug 13345)
The following bugs have been fixed:
* TCP reassembly: tcp.reassembled_in is not set in first packet.
([5]Bug 3264)
* Duplicated Interfaces instances while refreshing. ([6]Bug 11553)
* Time zone name needs to be converted to UTF-8 on Windows. ([7]Bug
11785)
* Crash on fast local interface changes. ([8]Bug 12263)
* Please align columns in tshark's output. ([9]Bug 12502)
* Display data rate fields for VHT rates invalid with BCC modulation.
([10]Bug 12859)
* plugin_if_get_ws_info causes Access Violation if called during
rescan. ([11]Bug 12973)
* SMTP BDAT dissector not reverting to command-code after DATA.
([12]Bug 13030)
* Wireshark fails to recognize V6 DBS Etherwatch capture files.
([13]Bug 13093)
* Runtime Error when try to merge .pcap files (Wireshark crashes).
([14]Bug 13175)
* PPP BCP BPDU size reports not header size, but all data underneath
and its header size in UI. ([15]Bug 13188)
* In-line UDP checksum bytes in 6LoWPAN IPHC are swapped. ([16]Bug
13233)
* Uninitialized memcmp on data in daintree-sna.c. ([17]Bug 13246)
* Crash when dissect WDBRPC Version 2 protocol with Dissect unknown
program numbers enabled. ([18]Bug 13266)
* Contents/Resources/bin directory isn't in the app bundle after
installation. ([19]Bug 13270)
* Regression: IEEE17221 (AVDECC) decoded as IEEE1722 (AVB
Transportation Protocol). ([20]Bug 13274)
* Can't decode packets captured with OpenBSD enc(4) encapsulating.
([21]Bug 13279)
* UDLD flags are at other end of octet. ([22]Bug 13280)
* MS-WSP dissector no longer works since commit
8c2fa5b5cf789e6d0d19cd0dd34479d0203d177a. ([23]Bug 13299)
* TBCD string decoded wrongly in MAP ATI message. ([24]Bug 13316)
* Filter Documentation: The tilde (~) operator is not documented.
([25]Bug 13320)
* VoIP Flow Sequence Causes Application Crash. ([26]Bug 13329)
New and Updated Features
There are no new features in this release.
New File Format Decoding Support
There are no new file formats in this release.
New Protocol Support
There are no new protocols in this release.
Updated Protocol Support
6LoWPAN, DVB-CI, ENC, GSM MAP, IEEE 1722, IEEE 1722.1, ISAKMP, MS-WSP,
PPP, QUIC, Radiotap, RPC, SMTP, TCP, UCD, and UDLD
New and Updated Capture File Support
There is no new or updated capture file support in this release.
Daintree SNA, and DBS Etherwatch
New and Updated Capture Interfaces support
There are no new or updated capture interfaces supported in this
release.
Major API Changes
There are no major API changes in this release.
__________________________________________________________________
Getting Wireshark
Wireshark source code and installation packages are available from
[27]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 [28]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. ([29]Bug 1419)
The BER dissector might infinitely loop. ([30]Bug 1516)
Capture filters aren't applied when capturing from named pipes.
([31]Bug 1814)
Filtering tshark captures with read filters (-R) no longer works.
([32]Bug 2234)
Application crash when changing real-time option. ([33]Bug 4035)
Wireshark and TShark will display incorrect delta times in some cases.
([34]Bug 4985)
Wireshark should let you work with multiple capture files. ([35]Bug
10488)
Dell Backup and Recovery (DBAR) makes many Windows applications crash,
including Wireshark. ([36]Bug 12036)
__________________________________________________________________
Getting Help
Community support is available on [37]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 [38]the web site.
Official Wireshark training and certification are available from
[39]Wireshark University.
__________________________________________________________________
Frequently Asked Questions
A complete FAQ is available on the [40]Wireshark web site.
__________________________________________________________________
Last updated 2017-01-23 20:21:22 UTC
References
1. https://www.wireshark.org/security/wnpa-sec-2017-01.html
2. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=13344
3. https://www.wireshark.org/security/wnpa-sec-2017-02.html
4. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=13345
5. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=3264
6. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=11553
7. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=11785
8. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=12263
9. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=12502
10. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=12859
11. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=12973
12. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=13030
13. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=13093
14. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=13175
15. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=13188
16. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=13233
17. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=13246
18. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=13266
19. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=13270
20. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=13274
21. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=13279
22. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=13280
23. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=13299
24. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=13316
25. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=13320
26. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=13329
27. https://www.wireshark.org/download.html
28. https://www.wireshark.org/download.html#thirdparty
29. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=1419
30. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=1516
31. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=1814
32. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=2234
33. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=4035
34. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=4985
35. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=10488
36. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=12036
37. https://ask.wireshark.org/
38. https://www.wireshark.org/lists/
39. http://www.wiresharktraining.com/
40. https://www.wireshark.org/faq.html
Digests
wireshark-2.2.4.tar.bz2: 32336156 bytes
SHA256(wireshark-2.2.4.tar.bz2)=42a7fb35eed5a32478153e24601a284bb50148b7ba919c3e8452652f4c2a3911
RIPEMD160(wireshark-2.2.4.tar.bz2)=82b8df88a97c8fe0608ff8b099e366ca4eb620d1
SHA1(wireshark-2.2.4.tar.bz2)=2913835d17a93af2a85ad5d9b580c47b359619a4
MD5(wireshark-2.2.4.tar.bz2)=6d0878ba931ea379f6e675d4cba6536b
Wireshark-win32-2.2.4.exe: 44516632 bytes
SHA256(Wireshark-win32-2.2.4.exe)=2c36978d0367aac1881d68ede14dcbd8003b78a45a30a30dc5086bf7ccc64d48
RIPEMD160(Wireshark-win32-2.2.4.exe)=5ff5129dfc858e97584870b94d28493d29af1f30
SHA1(Wireshark-win32-2.2.4.exe)=18554bb841a1fc988bed335f134f6ec429f67e21
MD5(Wireshark-win32-2.2.4.exe)=5c23a3735595445a6e612551fab6be4e
Wireshark-win64-2.2.4.exe: 49360976 bytes
SHA256(Wireshark-win64-2.2.4.exe)=0dabf7f5cba2101ef9303a50c81ef9eb9d59738ff62b4f4c5bba5a15ca4671f8
RIPEMD160(Wireshark-win64-2.2.4.exe)=04a0ea2349f24fd0ae244ecfb23aa0114526afc6
SHA1(Wireshark-win64-2.2.4.exe)=13cc7e778041ee986dabd0b2f1923a031c8965ae
MD5(Wireshark-win64-2.2.4.exe)=8b477478d5d9ce9cc808f8539f515d13
WiresharkPortable_2.2.4.paf.exe: 46090528 bytes
SHA256(WiresharkPortable_2.2.4.paf.exe)=e34cb1610f82a87469108ee542ea1b703f840b84105c997bd78c7daa5f152495
RIPEMD160(WiresharkPortable_2.2.4.paf.exe)=64b28d94f7af237e165650618f88eb1a551fc67e
SHA1(WiresharkPortable_2.2.4.paf.exe)=46fb03f252b26f35829b22c2ef178ce6034f055e
MD5(WiresharkPortable_2.2.4.paf.exe)=79b798f3d6d21284e0f6eaf2c2f4c837
Wireshark 2.2.4 Intel 64.dmg: 32844200 bytes
SHA256(Wireshark 2.2.4 Intel
64.dmg)=e3951fdd6cbf7bfec65595ba668f953ccb2587ad94f078cac3a5b99bf3bd2e6e
RIPEMD160(Wireshark 2.2.4 Intel
64.dmg)=3ca1f000fbd7f9de77a26607863b964f005883b9
SHA1(Wireshark 2.2.4 Intel 64.dmg)=f571e5c36249c9e27acd1075b6bb083cb44a8395
MD5(Wireshark 2.2.4 Intel 64.dmg)=4d9eb54c726b86873c42d3ad0b06f3d4
Attachment:
signature.asc
Description: OpenPGP digital signature
- Prev by Date: [Wireshark-dev] Wireshark 2.0.10 is now available
- Next by Date: Re: [Wireshark-dev] Same issue of compiling wireshark on AWS AMI
- Previous by thread: [Wireshark-dev] Wireshark 2.0.10 is now available
- Next by thread: [Wireshark-dev] New GUI for specific protocol
- Index(es):