[Gerald Combs <gerald@xxxxxxxxxxxxx>]

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

I'm proud to announce the release of Wireshark 1.10.0rc2.

     __________________________________________________________

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:
     * Redirecting the standard output didn't redirect the output
       the of -D or -L flags. This fix means that the output of
       those flags now goes to the standard output, not the
       standard error, as it did in previous releases. [1]Bug 8609

  New and Updated Features

   The following features are new (or have been significantly
   updated) since version 1.8:
     * Wireshark on 32- and 64-bit Windows supports automatic
       updates.
     * The packet bytes view is faster.
     * You can now display a list of resolved host names in
       "hosts" format within Wireshark.
     * The wireless toolbar has been updated.
     * Wireshark on Linux does a better job of detecting interface
       addition and removal.
     * It is now possible to compare two fields in a display
       filter (for example: udp.srcport != udp.dstport). The two
       fields must be of the same type for this to work.
     * The Windows installers ship with WinPcap 4.1.3, which
       supports Windows 8.
     * USB type and product name support has been improved.
     * All Bluetooth profiles and protocols are now supported.
     * Wireshark now calculates HTTP response times and presents
       the result in a new field in the HTTP response. Links from
       the request's frame to the response's frame and vice-versa
       are also added.
     * The main welcome screen and status bar now display file
       sizes using strict SI prefixes instead of old-style binary
       prefixes.
     * Capinfos now prints human-readable statistics with SI
       suffixes by default.
     * It is now possible to open a referenced packet (such as the
       matched request or response packet) in a new window.
     * Tshark can now display only the hex/ascii packet data
       without requiring that the packet summary and/or packet
       details are also displayed. If you want the old behavior,
       use -Px instead of just -x.
     * Wireshark can be compiled using GTK+ 3.
     * The Wireshark application icon, capture toolbar icons, and
       other icons have been updated.
     * Tshark's filtering and multi-pass analysis have been
       reworked for consistency and in order to support dependent
       frame calculations during reassembly. See the man page
       descriptions for -2, -R, and -Y.
     * Tshark's -G fields2 and -G fields3 options have been
       eliminated. The -G fields option now includes the 2 extra
       fields that -G fields3 previously provided, and the blurb
       information has been relegated to the last column since in
       many cases it is blank anyway.
     * Wireshark dropped the left-handed settings from the
       preferences. This is still configurable via the GTK
       settings (add "gtk-scrolled-window-placement = top-right"
       in the config file, which might be called [/.gtkrc-2.0 or
       ]/.config/gtk-3.0/settings.ini).
     * Wireshark now ships with two global configuration files:
       Bluetooth, which contains coloring rules for Bluetooth and
       Classic, which contains the old-style coloring rules.

  New Protocol Support

   Amateur Radio AX.25, Amateur Radio BPQ, Amateur Radio NET/ROM,
   America Online (AOL), AR Drone, Automatic Position Reporting
   System (APRS), AX.25 KISS, AX.25 no Layer 3, Bitcoin Protocol,
   Bluetooth Attribute Protocol, Bluetooth AVCTP Protocol,
   Bluetooth AVDTP Protocol, Bluetooth AVRCP Profile, Bluetooth
   BNEP Protocol, Bluetooth HCI USB Transport, Bluetooth HCRP
   Profile, Bluetooth HID Profile, Bluetooth MCAP Protocol,
   Bluetooth SAP Profile, Bluetooth SBC Codec, Bluetooth Security
   Manager Protocol, Cisco GED-125 Protocol, Clique Reliable
   Multicast Protocol (CliqueRM), D-Bus, Digital Transmission
   Content Protection over IP, DVB-S2 Baseband, FlexNet,
   Forwarding and Control Element Separation Protocol (ForCES),
   Foundry Discovery Protocol (FDP), Gearman Protocol, GEO-Mobile
   Radio (1) RACH, HoneyPot Feeds Protocol (HPFEEDS), LTE
   Positioning Protocol Extensions (LLPe), Media Resource Control
   Protocol Version 2 (MRCPv2), Media-Independent Handover (MIH),
   MIDI System Exclusive (SYSEX), Mojito DHT, MPLS-TP
   Fault-Management, MPLS-TP Lock-Instruct, NASDAQ's OUCH 4.x,
   NASDAQ's SoupBinTCP, OpenVPN Protocol, Pseudo-Wire OAM,
   RPKI-Router Protocol, SEL Fast Message, Simple Packet Relay
   Transport (SPRT), Skype, Smart Message Language (SML), SPNEGO
   Extended Negotiation Security Mechanism (NEGOEX), UHD/USRP, USB
   Audio, USB Video, v.150.1 State Signaling Event (SSE), VITA 49
   Radio Transport, VNTAG, WebRTC Datachannel Protocol (RTCDC),
   and WiMAX OFDMA PHY SAP

  Updated Protocol Support

   Too many protocols have been updated to list here.

  New and Updated Capture File Support

   AIX iptrace, CAM Inspector, Catapult DCT2000, Citrix NetScaler,
   DBS Etherwatch (VMS), Endace ERF, HP-UX nettl, IBM iSeries,
   Ixia IxVeriWave, NA Sniffer (DOS), Netscreen, Network
   Instruments Observer, pcap, pcap-ng, Symbian OS btsnoop,
   TamoSoft CommView, and Tektronix K12xx
     __________________________________________________________

Getting Wireshark

   Wireshark source code and installation packages are available
   from [2]http://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.
   (ws-buglink:1814)

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

   The 64-bit Windows installer does not support Kerberos
   decryption. ([7]Win64 development page)

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

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

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

   Summary pane selected frame highlighting not maintained.
   ([11]Bug 4445)

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

Getting Help

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

   Official Wireshark training and certification are available
   from [15]Wireshark University.
     __________________________________________________________

Frequently Asked Questions

   A complete FAQ is available on the [16]Wireshark web site.
     __________________________________________________________

   Last updated 2013-05-20 15:54:29 PDT

References

   1. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=8609
   2. http://www.wireshark.org/download.html
   3. http://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=2234
   7. https://wiki.wireshark.org/Development/Win64
   8. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=4035
   9. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=4056
  10. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=4357
  11. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=4445
  12. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=4985
  13. http://ask.wireshark.org/
  14. http://www.wireshark.org/lists/
  15. http://www.wiresharktraining.com/
  16. http://www.wireshark.org/faq.html


Digests

wireshark-1.10.0rc2.tar.bz2: 27099146 bytes
MD5(wireshark-1.10.0rc2.tar.bz2)=17fade46415df20d1bad4ed1f2e326b1
SHA1(wireshark-1.10.0rc2.tar.bz2)=b900869e904c20fb9314f82a530f60ff2f0f7d5b
RIPEMD160(wireshark-1.10.0rc2.tar.bz2)=b2dbea92949d6fc1d20bb88bbf77e79f475d1a8c

Wireshark-win32-1.10.0rc2.exe: 22235680 bytes
MD5(Wireshark-win32-1.10.0rc2.exe)=44d090c0eccf3c1d3fcbf7b00a5770f1
SHA1(Wireshark-win32-1.10.0rc2.exe)=54d8bb63854621740d7ba3608427f9917d4e47fb
RIPEMD160(Wireshark-win32-1.10.0rc2.exe)=b1d67074791f9413e2da62e926b827ac594b95f6

Wireshark-win64-1.10.0rc2.exe: 28087200 bytes
MD5(Wireshark-win64-1.10.0rc2.exe)=63a6628cd2bb922ee78a7392b56a281d
SHA1(Wireshark-win64-1.10.0rc2.exe)=36487e88e494462029341f8fa3f7e7a99b4961af
RIPEMD160(Wireshark-win64-1.10.0rc2.exe)=c81dfdece3e66b67219d1f07129bb70f8c88631d

Wireshark-1.10.0rc2.u3p: 30769965 bytes
MD5(Wireshark-1.10.0rc2.u3p)=a1600915015ccd7544d5b76b5bcb4531
SHA1(Wireshark-1.10.0rc2.u3p)=a8f687ef881382a7ae4988f906842c76a8df2112
RIPEMD160(Wireshark-1.10.0rc2.u3p)=20f523e5a4242f16d1c73456b45c9a2a3601da47

WiresharkPortable-1.10.0rc2.paf.exe: 23590992 bytes
MD5(WiresharkPortable-1.10.0rc2.paf.exe)=7c964ad2320669d72a2a0175660b5680
SHA1(WiresharkPortable-1.10.0rc2.paf.exe)=c414bc92fc1967c0e48b4e57daffa22b231f00db
RIPEMD160(WiresharkPortable-1.10.0rc2.paf.exe)=adf8675865e49a11efec2b629cd0a7cb194f082c

Wireshark 1.10.0rc2 Intel 32.dmg: 21857055 bytes
MD5(Wireshark 1.10.0rc2 Intel 32.dmg)=4388c85a0798711ceb31eefe6a68c2e9
SHA1(Wireshark 1.10.0rc2 Intel
32.dmg)=ded00b6cd181c363c64cdfd6c2085e6c38ab9286
RIPEMD160(Wireshark 1.10.0rc2 Intel
32.dmg)=f4f4c98e5239c5e306ab24344dc9e876a694d1ce

Wireshark 1.10.0rc2 Intel 64.dmg: 23911090 bytes
MD5(Wireshark 1.10.0rc2 Intel 64.dmg)=19a4182283619779bc9ebe94646d228d
SHA1(Wireshark 1.10.0rc2 Intel
64.dmg)=c93bdd65079702776fbcea24205fb34f124e8276
RIPEMD160(Wireshark 1.10.0rc2 Intel
64.dmg)=80ee27ce020390f961bafced694c0b8e973c118b
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (Darwin)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iEYEARECAAYFAlGdWYUACgkQpw8IXSHylJqm9ACgi5k21G2l/jKfUpB536Mud47x
uzkAmgIesFaV/vH+DfYCbF1VfEDnu7WU
=dKkF
-----END PGP SIGNATURE-----