[prev in list] [next in list] [prev in thread] [next in thread]
List: wireshark-users
Subject: [Wireshark-users] Wireshark 2.4.3 is now available
From: Gerald Combs <gerald () wireshark ! org>
Date: 2017-11-30 21:55:51
Message-ID: 576bf9b2-8a29-4489-e3f6-d1d502686c9e () wireshark ! org
[Download RAW message or body]
[Attachment #2 (multipart/signed)]
[Attachment #4 (multipart/mixed)]
I'm proud to announce the release of Wireshark 2.4.3.
__________________________________________________________________
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-47
The IWARP_MPA dissector could crash. ([2]Bug 14236)
* [3]wnpa-sec-2017-48
The NetBIOS dissector could crash. ([4]Bug 14249)
* [5]wnpa-sec-2017-49
The CIP Safety dissector could crash. ([6]Bug 14250)
* "tshark -G ?" doesn't provide expected help. ([7]Bug 13984)
* File loading is very slow with TRANSUM dissector enabled. ([8]Bug
14094)
* packet-knxnetip.c:936: bad bitmask ?. ([9]Bug 14115)
* packet-q931.c:1306: bad compare ?. ([10]Bug 14116)
* SSL Dissection bug. ([11]Bug 14117)
* Wireshark crashes when exporting various files to .csv, txt and
other `non-capture file' formats. ([12]Bug 14128)
* RLC reassembly doesn't work for RLC over UDP heuristic dissector.
([13]Bug 14129)
* HTTP Object export fails with long extension (possibly query
string). ([14]Bug 14130)
* 3GPP Civic Address not displayed in Packet Details. ([15]Bug 14131)
* Wireshark prefers packet.dll in System32\\Npcap over the one in
System32. ([16]Bug 14134)
* PEEKREMOTE dissector does not decode 11ac MCS rates properly.
([17]Bug 14136)
* Visual Studio Community Edition 2015 lacks tools named in developer
guide. ([18]Bug 14147)
* TCP: Malformed data with Riverbed Probe option. ([19]Bug 14150)
* Wireshark Crash when trying to use Preferences | Advanced. ([20]Bug
14157)
* Right click on SMB2 Message ID and then Apply as Column causes
Runtime Error. ([21]Bug 14169)
* Return [Enter] should apply change (Column title - Button Label
toolbars). ([22]Bug 14191)
* Wireshark crashes if "rip.display_routing_domain" is set to TRUE in
preferences file. ([23]Bug 14197)
* Entry point inflatePrime not found for androiddump.exe and
randpktdump.exe. ([24]Bug 14207)
* BGP: IPv6 NLRI is received with Add-path ID, then Wire shark is not
able to decode the packet correctly. ([25]Bug 14241)
* Wrong SSL decryption when using EXTENDED MASTER SECRET and Client
certificate request (mutual authentication). ([26]Bug 14243)
* Frame direction isn't always set if it comes from the pcapng record
header rather than the packet pseudo-header. ([27]Bug 14245)
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
3GPP NAS, BGP, CIP Safety, DTLS, IEEE 802.11 Radio, IWARP_MPA,
KNXnet/IP, LCSAP, MQTT, NetBIOS, PEEKREMOTE, Q.931, RIP, RLC, SIP,
SSL/TLS, TCP, and TRANSUM
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
[28]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 [29]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. ([30]Bug 1419)
The BER dissector might infinitely loop. ([31]Bug 1516)
Capture filters aren't applied when capturing from named pipes.
([32]Bug 1814)
Filtering tshark captures with read filters (-R) no longer works.
([33]Bug 2234)
Application crash when changing real-time option. ([34]Bug 4035)
Wireshark and TShark will display incorrect delta times in some cases.
([35]Bug 4985)
Wireshark should let you work with multiple capture files. ([36]Bug
10488)
__________________________________________________________________
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-11-30 19:27:06 UTC
References
1. https://www.wireshark.org/security/wnpa-sec-2017-47.html
2. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14236
3. https://www.wireshark.org/security/wnpa-sec-2017-48.html
4. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14249
5. https://www.wireshark.org/security/wnpa-sec-2017-49.html
6. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14250
7. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=13984
8. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14094
9. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14115
10. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14116
11. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14117
12. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14128
13. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14129
14. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14130
15. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14131
16. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14134
17. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14136
18. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14147
19. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14150
20. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14157
21. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14169
22. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14191
23. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14197
24. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14207
25. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14241
26. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14243
27. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14245
28. https://www.wireshark.org/download.html
29. https://www.wireshark.org/download.html#thirdparty
30. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=1419
31. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=1516
32. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=1814
33. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=2234
34. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=4035
35. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=4985
36. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=10488
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.4.3.tar.xz: 28807920 bytes
SHA256(wireshark-2.4.3.tar.xz)=d6378d0989e3e3eb4565fde58a2691d123105b52e436991f01f9709063534678
RIPEMD160(wireshark-2.4.3.tar.xz)=41cec30fcaf6f307d660a4f27730364868c8584a
SHA1(wireshark-2.4.3.tar.xz)=c7ca0fa4b9983a200c88b91f7dccc7369a99af42
Wireshark-win32-2.4.3.exe: 52674464 bytes
SHA256(Wireshark-win32-2.4.3.exe)=3c8a792fd4da80ab392b74b0e02f4f1ee1a91343bc34bbb312ef057da1962228
RIPEMD160(Wireshark-win32-2.4.3.exe)=a1020d967800baa65209ca26a3544ec6f4509a0f
SHA1(Wireshark-win32-2.4.3.exe)=d716f8631750aa9dd6376ac6156a52ffbe412b42
Wireshark-win64-2.4.3.exe: 57888152 bytes
SHA256(Wireshark-win64-2.4.3.exe)=2037401580a97f48bdeef06c4ff0716d4874a24eeebb0f6b494a4c6abe86140a
RIPEMD160(Wireshark-win64-2.4.3.exe)=76ca73ee5a2ef4137577b90d3f392c0c1579f75e
SHA1(Wireshark-win64-2.4.3.exe)=cf94cbcd3d9452d413e7f06180a9f3edd226e779
Wireshark-win32-2.4.3.msi: 41930752 bytes
SHA256(Wireshark-win32-2.4.3.msi)=5ffa5e61b6d867f2eb1b45ace419b95fe0807f54e0e0215af22ba322d946f326
RIPEMD160(Wireshark-win32-2.4.3.msi)=53fc463c40ec8010fb9d5ae5a02c8c2494912c25
SHA1(Wireshark-win32-2.4.3.msi)=652528b474ed1b86b72057ecb6be287987b93297
Wireshark-win64-2.4.3.msi: 47005696 bytes
SHA256(Wireshark-win64-2.4.3.msi)=db94ee7bbb7c7b9d87692813afe31f79bf16cd03e57eb2807be538830ddfaec1
RIPEMD160(Wireshark-win64-2.4.3.msi)=662507de13cf32c0532b3c5caedc2c5d4592feb6
SHA1(Wireshark-win64-2.4.3.msi)=e0dedcc4dd0c83d61eb232413cbe6773418fa6a1
WiresharkPortable_2.4.3.paf.exe: 45325376 bytes
SHA256(WiresharkPortable_2.4.3.paf.exe)=357e99cdb339fbd6d55baa6bad1ce096c9ae4371813be25506edda8edaf5b14d
RIPEMD160(WiresharkPortable_2.4.3.paf.exe)=1edd262990a1056e33285ea24c96340ca2dab0a6
SHA1(WiresharkPortable_2.4.3.paf.exe)=1f4b57a6adbdde137141089cebb8a2f0aea948f8
Wireshark 2.4.3 Intel 64.dmg: 35234122 bytes
SHA256(Wireshark 2.4.3 Intel
64.dmg)=020a4cd8e4da3e8f70ea01ba30ace9a0b86b68363f2a179681172bdb54235550
RIPEMD160(Wireshark 2.4.3 Intel
64.dmg)=6f6341b720a4f974f72fdbbda443291d91e1594c
SHA1(Wireshark 2.4.3 Intel 64.dmg)=122e37fc6c062984ad657de16ae04dec3046a801
You can validate these hashes using the following commands (among others):
Windows: certutil -hashfile Wireshark-win64-x.y.z.exe SHA256
Linux (GNU Coreutils): sha256sum wireshark-x.y.z.tar.xz
macOS: shasum -a 256 "Wireshark x.y.z Intel 64.dmg"
Other: openssl sha256 wireshark-x.y.z.tar.xz
["signature.asc" (application/pgp-signature)]
[Attachment #8 (text/plain)]
___________________________________________________________________________
Sent via: Wireshark-users mailing list <wireshark-users@wireshark.org>
Archives: https://www.wireshark.org/lists/wireshark-users
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-users
mailto:wireshark-users-request@wireshark.org?subject=unsubscribe
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic