Wireshark-users: Re: [Wireshark-users] Wireshark 1.99.2 is now available

Date: Fri, 06 Feb 2015 16:57:34 -0500
Congratulations Gerald and Wireshark Team......awesome!

Sent from my Verizon Wireless - Tim@xxxxxxxxxxxxxx


Gerald Combs <gerald@xxxxxxxxxxxxx> wrote:

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

I'm proud to announce the release of Wireshark 1.99.2.


   This is an experimental release intended to test new features for
   Wireshark 2.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 1.99.1:
     * Qt port:
          + The welcome screen layout has been updated.
          + The Preferences dialog no longer crashes on Windows.
          + The packet list header menu has been added.
          + Statistics tree plugins are now supported.
          + The window icon is now displayed properly in the Windows
            taskbar.
          + A packet list an byte view selection bug has been fixed
            ([1]Bug 10896)
          + The RTP Streams dialog has been added.
          + The Protocol Hierarchy Statistics dialog has been added.

   The following features are new (or have been significantly updated)
   since version 1.99.0:
     * Qt port:
          + You can now show and hide toolbars and major widgets using the
            View menu.
          + You can now set the time display format and precision.
          + The byte view widget is much faster, particularly when
            selecting large reassembled packets.
          + The byte view is explorable. Hovering over it highlights the
            corresponding field and shows a description in the status bar.
          + An Italian translation has been added.
          + The Summary dialog has been updated and renamed to Capture
            File Properties.
          + The VoIP Calls and SIP Flows dialogs have been added.
          + Support for HiDPI / Retina displays has been improved in the
            official packages.
     * DNS stats: + A new stats tree has been added to the Statistics
       menu. Now it is possible to collect stats such as qtype/qclass
       distribution, number of resource record per response section, and
       stats data (min, max, avg) for values such as query name length or
       DNS payload.
     * HPFEEDS stats: + A new stats tree has been added to the statistics
       menu. Now it is possible to collect stats per channel (messages
       count and payload size), and opcode distribution.
     * HTTP2 stats: + A new stats tree has been added to the statistics
       menu. Now it is possible to collect stats (type distribution).

   The following features are new (or have been significantly updated)
   since version 1.12.0:
     * The I/O Graph in the Gtk+ UI now supports an unlimited number of
       data points (up from 100k).
     * TShark now resets its state when changing files in ring-buffer
       mode.
     * Expert Info severities can now be configured.
     * Wireshark now supports external capture interfaces. External
       capture interfaces can be anything from a tcpdump-over-ssh pipe to
       a program that captures from proprietary or non-standard hardware.
       This functionality is not available in the Qt UI yet.
     * Qt port:
          + The Qt UI is now the default (program name is wireshark).
          + A Polish translation has been added.
          + The Interfaces dialog has been added.
          + The interface list is now updated when interfaces appear or
            disappear.
          + The Conversations and Endpoints dialogs have been added.
          + A Japanese translation has been added.
          + It is now possible to manage remote capture interfaces.
          + Windows: taskbar progress support has been added.
          + Most toolbar actions are in place and work.
          + More command line options are now supported

  New Protocol Support

   (LISP) TCP Control Message, AllJoyn Reliable Datagram Protocol, Android
   ADB, Android Logcat text, ceph, corosync/totemnet, corosync/totemsrp,
   Couchbase, CP "Cooper" 2179, DJI UAV Drone Control Protocol, Dynamic
   Source Routing (RFC 4728), Elasticsearch, ETSI Card Application Toolkit
   - Transport Protocol, Generic Network Virtualization Encapsulation
   (Geneve), GVSP, HCrt, HiQnet, IPMI Trace, iSER, KNXnetIP, MACsec Key
   Agreement - EAPoL-MKA, MCPE (Minecraft Pocket Edition), OptoMMP, RakNet
   games library, Riemann, S7 Communication, Shared Memory Communications
   - RDMA, Stateless Transport Tunneling, and ZVT Kassenschnittstelle

  Updated Protocol Support

   Too many protocols have been updated to list here.

  New and Updated Capture File Support

   Android Logcat text files, Colasoft Capsa files, and Wireshark now
   supports nanosecond timestamp resolution in PCAP-NG files.

  Major API Changes

   The libwireshark API has undergone some major changes:
     * The emem framework (including all ep_ and se_ memory allocation
       routines) has been completely removed in favour of wmem which is
       now fully mature.
     * The (long-since-broken) Python bindings support has been removed.
       If you want to write dissectors in something other than C, use Lua.
     __________________________________________________________________

Getting Wireshark

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

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

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

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

   Resolving ([8]Bug 9044) reopens ([9]Bug 3528) so that Wireshark no
   longer automatically decodes gzip data when following a TCP stream.

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

   Hex pane display issue after startup. ([11]Bug 4056)

   Packet list rows are oversized. ([12]Bug 4357)

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

   The 64-bit version of Wireshark will leak memory on Windows when the
   display depth is set to 16 bits ([14]Bug 9914)

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

Getting Help

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

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

Frequently Asked Questions

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

   Last updated 2015-02-04 20:19:34 UTC

References

   1. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=10896
   2. https://www.wireshark.org/download.html
   3. https://www.wireshark.org/download.html#thirdparty
   4. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=1419
   5. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=1516
   6. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=1814
   7. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=2234
   8. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=9044
   9. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=3528
  10. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=4035
  11. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=4056
  12. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=4357
  13. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=4985
  14. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=9914
  15. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=10488
  16. http://ask.wireshark.org/
  17. https://www.wireshark.org/lists/
  18. http://www.wiresharktraining.com/
  19. https://www.wireshark.org/faq.html


Digests

wireshark-1.99.2.tar.bz2: 30265896 bytes
MD5(wireshark-1.99.2.tar.bz2)=f8f45738b3e849af31737d9607e098e2
SHA1(wireshark-1.99.2.tar.bz2)=8baea1300cca0fe4e5c552113e3521dc8fccdb48
RIPEMD160(wireshark-1.99.2.tar.bz2)=d84c5e05f796309fc9450b40a4b50bebce48e9f9

Wireshark-win64-1.99.2.exe: 44702952 bytes
MD5(Wireshark-win64-1.99.2.exe)=752da6e95d58d4928b1d6652d3bd0e94
SHA1(Wireshark-win64-1.99.2.exe)=c3d982cb47338208980942b07da02996128b3dca
RIPEMD160(Wireshark-win64-1.99.2.exe)=9020516bd191e279f2bde8446240f4b135600f47

Wireshark-win32-1.99.2.exe: 35816848 bytes
MD5(Wireshark-win32-1.99.2.exe)=21833c8761dff90f6804b59336563e76
SHA1(Wireshark-win32-1.99.2.exe)=cb2d288aedf910c32ab2891b5009a3142f6c3681
RIPEMD160(Wireshark-win32-1.99.2.exe)=2016b1d22e5fb313b44b1655bfeba5f2f34a7a9b

WiresharkPortable_1.99.2.paf.exe: 29427184 bytes
MD5(WiresharkPortable_1.99.2.paf.exe)=f163c5115b8a18aee4729a48b475b937
SHA1(WiresharkPortable_1.99.2.paf.exe)=369400cc9efdda693f0a5a6b9a26b2fa34a3d327
RIPEMD160(WiresharkPortable_1.99.2.paf.exe)=7ba07dca22e70913bf0862b0a209bae249846924

Wireshark 1.99.2 Intel 64.dmg: 43151377 bytes
MD5(Wireshark 1.99.2 Intel 64.dmg)=9f8e7429eebaca5e7ccb5615c6fb21ca
SHA1(Wireshark 1.99.2 Intel
64.dmg)=64c427dd8faed77b4af46903095a13c617b661c0
RIPEMD160(Wireshark 1.99.2 Intel
64.dmg)=4ccb288c1b472c8d4dde9d49c0476a2b126f544b

Wireshark 1.99.2 Intel 32.dmg: 33354903 bytes
MD5(Wireshark 1.99.2 Intel 32.dmg)=dfd2b4b137efbdb17bccc13ceea36ee5
SHA1(Wireshark 1.99.2 Intel
32.dmg)=2af2148d666180e90f923eccd69d480fbd806aec
RIPEMD160(Wireshark 1.99.2 Intel
32.dmg)=cb4835cf12b84dacac4e14bde854caad01aa4081
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iEYEARECAAYFAlTShWoACgkQpw8IXSHylJrdcgCgxkbbIJdYrVkjfeksjTY+HkEw
XUYAoJ225GGf9SE5YTAD+CnDMpP01jKP
=mhkX
-----END PGP SIGNATURE-----
___________________________________________________________________________
Sent via:    Wireshark-users mailing list <wireshark-users@xxxxxxxxxxxxx>
Archives:    http://www.wireshark.org/lists/wireshark-users
Unsubscribe: https://wireshark.org/mailman/options/wireshark-users
             mailto:wireshark-users-request@xxxxxxxxxxxxx?subject=unsubscribe