Wireshark-announce: [Wireshark-announce] Wireshark 2.4.0rc1 is now available
From: Wireshark announcements <[email protected]>
Date: Wed, 7 Jun 2017 17:54:38 -0700
I'm proud to announce the release of Wireshark 2.4.0rc1.


   This is the first release candidate for Wireshark 2.4.0.
     __________________________________________________________________

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

  New and Updated Features

   The following features are new (or have been significantly updated)
   since version 2.2.0:
     * Experimental 32-bit and 64-bit Windows Installer (.msi) packages
       are available. It is recommended that you use these independently
       of the NSIS (.exe) installers. That is, you should make sure the
       NSIS package is completely uninstalled before installing the
       Windows Installer package and vice-versa.
     * Source packages are now compressed using xz instead of bzip2.
     * The legacy (GTK+) UI is disabled by default in the Windows
       installer.
     * The legacy (GTK+) UI is disabled by default in Autotools and CMake.
     * SS7 Point Codes can now be resolved into names with a hosts-like
       file.
     * Wireshark can now go fullscreen to have more room for packets.
     * TShark can now export objects like the other GUI interfaces.
     * Support for G.722 and G.726 codecs in the RTP Player (via the
       SpanDSP library).
     * You can now choose the output device when playing RTP streams.
     * Added support for dissectors to include a unit name natively in
       their hf field. A field can now automatically append "seconds" or
       "ms" to its value without additional printf-style APIs.
     * The Default profile can now be reset to default values.
     * You can move back and forth in the selection history in the Qt UI.
     * IEEE 802.15.4 dissector now uses an UAT for decryption keys. The
       original decryption key preference has been obsoleted.
     * Extcap utilities can now provide configuration for a GUI interface
       toolbar to control the extcap utility while capturing.
     * Extcap utilities can now validate the capture filter.
     * Display filter function len() can now be used on all string and
       byte fields.
     * Added timeline view for 802.11 wireless packet data.

  New Protocol Support

   (Facebook) Zero, Bluetooth HCI Vendor Intel, CAN FD, DirectPlay 8
   protocol, Ericsson A-bis P-GSL, Ericsson A-bis TFP (Traffic Forwarding
   Protocol), Fc00/cjdns Protocol, Generic Netlink (genl), GSM Osmux,
   GSMTAP based logging, Health Level 7 (HL7), High-speed SECS message
   service (HSMS), HomePNA, IndigoCare iCall protocol, IndigoCare Netrix
   protocol, iPerf2, ISO 15765, Linux 802.11 Netlink (nl80211), Local
   Service Discovery (LSD), M2 Application Protocol, Mesh Link
   Establishment (MLE), Netgear Ensemble Protocol, NetScaler HA Protocol,
   NetScaler Metric Exchange Protocol, NetScaler RPC Protocol, NM
   protocol, Nordic BLE Sniffer, NVMe, NVMe Fabrics RDMA, OBD-II PIDs,
   OpenThread simulator, RFTap Protocol, SCTE-35 Digital Program Insertion
   Messages, Snort Post-dissector, Thread CoAP, Unified Diagnostic
   Services (UDS), vSocket, Windows Cluster Management API (clusapi), and
   X-Rite i1 Display Pro (and derivatives) USB protocol

  Updated Protocol Support

   Too many protocols have been updated to list here.

  New and Updated Capture File Support

   Non-empty section placeholder.

  New and Updated Capture Interfaces support

   Non-empty section placeholder.

   IEEE802.11: wlan_mgt display filter element got renamed to wlan.
   Libgcrypt is now a required dependency.
     __________________________________________________________________

Getting Wireshark

   Wireshark source code and installation packages are available from
   [1]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 [2]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. ([3]Bug 1419)

   The BER dissector might infinitely loop. ([4]Bug 1516)

   Capture filters aren't applied when capturing from named pipes. ([5]Bug
   1814)

   Filtering tshark captures with read filters (-R) no longer works.
   ([6]Bug 2234)

   Application crash when changing real-time option. ([7]Bug 4035)

   Wireshark and TShark will display incorrect delta times in some cases.
   ([8]Bug 4985)

   Wireshark should let you work with multiple capture files. ([9]Bug
   10488)

   Dell Backup and Recovery (DBAR) makes many Windows applications crash,
   including Wireshark. ([10]Bug 12036)
     __________________________________________________________________

Getting Help

   Community support is available on [11]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 [12]the web site.

   Official Wireshark training and certification are available from
   [13]Wireshark University.
     __________________________________________________________________

Frequently Asked Questions

   A complete FAQ is available on the [14]Wireshark web site.
     __________________________________________________________________

   Last updated 2017-06-07 21:59:45 UTC

References

   1. https://www.wireshark.org/download.html
   2. https://www.wireshark.org/download.html#thirdparty
   3. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=1419
   4. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=1516
   5. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=1814
   6. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=2234
   7. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=4035
   8. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=4985
   9. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=10488
  10. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=12036
  11. https://ask.wireshark.org/
  12. https://www.wireshark.org/lists/
  13. http://www.wiresharktraining.com/
  14. https://www.wireshark.org/faq.html


Digests

wireshark-2.4.0rc1.tar.xz: 29097628 bytes
SHA256(wireshark-2.4.0rc1.tar.xz)=902aa0f7dc9e14af98dbfa1669fe6ee049caeb763571ace426949d52df1dbfde
RIPEMD160(wireshark-2.4.0rc1.tar.xz)=142245d947880b7baf143b73771cbd29c52512b8
SHA1(wireshark-2.4.0rc1.tar.xz)=0a4ea643ef5f64c2b93f4f1d1c783db051c665a1
MD5(wireshark-2.4.0rc1.tar.xz)=d7b017d634c40319009b794b357f8a1c

Wireshark-win64-2.4.0rc1.exe: 57682024 bytes
SHA256(Wireshark-win64-2.4.0rc1.exe)=777712b2edbe1b306c56318255ed01f08d5356295d97b52f470735ce239e5e1a
RIPEMD160(Wireshark-win64-2.4.0rc1.exe)=e173f384abc8b8672aead8843ac992cb4d6492a1
SHA1(Wireshark-win64-2.4.0rc1.exe)=87039c739c99c74d7e39b5bcd4385670b1379c93
MD5(Wireshark-win64-2.4.0rc1.exe)=265ad76624df37ea611bc9e882893cc4

Wireshark-win32-2.4.0rc1.exe: 52469984 bytes
SHA256(Wireshark-win32-2.4.0rc1.exe)=cc4e48cae69c84a15704a2944c1fb21639d3f3e42c7988585cfc07c7f4c5853e
RIPEMD160(Wireshark-win32-2.4.0rc1.exe)=c15c2e0cae103e9a7d104a20c4b55b65aa9a4731
SHA1(Wireshark-win32-2.4.0rc1.exe)=4db093da891241037831275a57b04cd5c4b8107b
MD5(Wireshark-win32-2.4.0rc1.exe)=0d7dab03025eee7f6acf385e892a745b

WiresharkPortable_2.4.0rc1.paf.exe: 45074936 bytes
SHA256(WiresharkPortable_2.4.0rc1.paf.exe)=dc95aa2be23102ff10fb3133ee553d3fb138142e85bad769dcea0263c1c36fb7
RIPEMD160(WiresharkPortable_2.4.0rc1.paf.exe)=5bedfd1be2e50b03c1166339685646acfb93c71c
SHA1(WiresharkPortable_2.4.0rc1.paf.exe)=2994c2b3dda12ee9e6dff157cee49d4f0f972a29
MD5(WiresharkPortable_2.4.0rc1.paf.exe)=126ca6768bb8d79358bfa58a7a1530e4

Wireshark 2.4.0rc1 Intel 64.dmg: 33826559 bytes
SHA256(Wireshark 2.4.0rc1 Intel
64.dmg)=33786a3c49270e66ea86dd200832aae141511f4286fbee015e4f4de22b047821
RIPEMD160(Wireshark 2.4.0rc1 Intel
64.dmg)=baab0f74af6903b3d0736475e6e770d9967b28bd
SHA1(Wireshark 2.4.0rc1 Intel 64.dmg)=3bd395701b696c5c538181790f87ff910b30d1b0
MD5(Wireshark 2.4.0rc1 Intel 64.dmg)=0b5e9b81360c420e21b85f5608101aea

Attachment: signature.asc
Description: OpenPGP digital signature