Wireshark · Wireshark-users: Re: [Wireshark-users] [Wireshark-announce] Wireshark 1.10.0rc1 is now available

[Joachim Gann <joachim.gann@xxxxxxxx>]

Wireshark announcements <wireshark-announce@xxxxxxxxxxxxx> schrieb:

>-----BEGIN PGP SIGNED MESSAGE-----
>Hash: SHA1
>
>I'm proud to announce the release of Wireshark 1.10.0rc1. This is the
>first release candidate for Wireshark 1.10.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
>
>  Bug Fixes
>
>   The following bugs have been fixed:
>
>  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.
>
>  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 [1]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 [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.
>   (ws-buglink:1814)
>
>   Filtering tshark captures with read filters (-R) no longer
>   works. ([5]Bug 2234)
>
>   The 64-bit Windows installer does not support Kerberos
>   decryption. ([6]Win64 development page)
>
>   Application crash when changing real-time option. ([7]Bug 4035)
>
>   Hex pane display issue after startup. ([8]Bug 4056)
>
>   Packet list rows are oversized. ([9]Bug 4357)
>
>   Summary pane selected frame highlighting not maintained.
>   ([10]Bug 4445)
>
>   Wireshark and TShark will display incorrect delta times in some
>   cases. ([11]Bug 4985)
>     __________________________________________________________
>
>Getting Help
>
>   Community support is available on [12]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 [13]the web site.
>
>   Official Wireshark training and certification are available
>   from [14]Wireshark University.
>     __________________________________________________________
>
>Frequently Asked Questions
>
>   A complete FAQ is available on the [15]Wireshark web site.
>     __________________________________________________________
>
>   Last updated 2013-04-22 10:39:34 PDT
>
>References
>
>   1. http://www.wireshark.org/download.html
>   2. http://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=2234
>   6. https://wiki.wireshark.org/Development/Win64
>   7. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=4035
>   8. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=4056
>   9. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=4357
>  10. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=4445
>  11. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=4985
>  12. http://ask.wireshark.org/
>  13. http://www.wireshark.org/lists/
>  14. http://www.wiresharktraining.com/
>  15. http://www.wireshark.org/faq.html
>
>
>Digests
>
>wireshark-1.10.0rc1.tar.bz2: 27061529 bytes
>MD5(wireshark-1.10.0rc1.tar.bz2)=39298e1c8343d3fa1acbd77ab33503fe
>SHA1(wireshark-1.10.0rc1.tar.bz2)=d9d5e897c42def2a90b508fba0151a226abc41e4
>RIPEMD160(wireshark-1.10.0rc1.tar.bz2)=707a6e512a441ed428cb53abf3b04253d0ef36a8
>
>Wireshark-win64-1.10.0rc1.exe: 28079976 bytes
>MD5(Wireshark-win64-1.10.0rc1.exe)=231929c1b044d66683edc0b260d885a6
>SHA1(Wireshark-win64-1.10.0rc1.exe)=55a203223bb642f628335b72be3c23edd71c9b38
>RIPEMD160(Wireshark-win64-1.10.0rc1.exe)=051103a241c709559ecce0c08b5de87c01eaeff4
>
>Wireshark-win32-1.10.0rc1.exe: 22227088 bytes
>MD5(Wireshark-win32-1.10.0rc1.exe)=dc357a87d11088aa768cd715ef4f3ad9
>SHA1(Wireshark-win32-1.10.0rc1.exe)=90f9d2da7a674a632645a3b09bb9130ae9eb53e9
>RIPEMD160(Wireshark-win32-1.10.0rc1.exe)=5f34cb06bb7e8503ca602debab4b1faecc0d09b6
>
>Wireshark-1.10.0rc1.u3p: 30755518 bytes
>MD5(Wireshark-1.10.0rc1.u3p)=988e672fea36e05015f037471cd045bf
>SHA1(Wireshark-1.10.0rc1.u3p)=0922201c702b0a4ea0dad03d400a33b0cd1cf210
>RIPEMD160(Wireshark-1.10.0rc1.u3p)=a09f3d384b008bc8d9d37a713c5b0a998a2c0134
>
>WiresharkPortable-1.10.0rc1.paf.exe: 23584280 bytes
>MD5(WiresharkPortable-1.10.0rc1.paf.exe)=fc439acd380c792cc3917858113ef6a6
>SHA1(WiresharkPortable-1.10.0rc1.paf.exe)=65c129b7f3bbd4ba8d67559f6ee19631ac350d67
>RIPEMD160(WiresharkPortable-1.10.0rc1.paf.exe)=a22ac09043c6577a2ac45a7926d92b1fb51974de
>
>Wireshark 1.10.0rc1 Intel 32.dmg: 24153010 bytes
>MD5(Wireshark 1.10.0rc1 Intel 32.dmg)=c828d4188e329c865cbb711ab93efe3e
>SHA1(Wireshark 1.10.0rc1 Intel
>32.dmg)=9ac20ec957a3d4a372bf93319a2ce107a8a1a15d
>RIPEMD160(Wireshark 1.10.0rc1 Intel
>32.dmg)=cb3ef75ddf48ac39eafe866876f54ed193a57e11
>
>Wireshark 1.10.0rc1 Intel 64.dmg: 24024741 bytes
>MD5(Wireshark 1.10.0rc1 Intel 64.dmg)=7628f6ef0d85960443a6cac147dd0455
>SHA1(Wireshark 1.10.0rc1 Intel
>64.dmg)=d0b49d77671800d2a52cec6e478e826bb8ac5a02
>RIPEMD160(Wireshark 1.10.0rc1 Intel
>64.dmg)=81ff48a31c067166b9ec65acf3c66824333e7019
>-----BEGIN PGP SIGNATURE-----
>Version: GnuPG v1.4.12 (Darwin)
>Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
>
>iEYEARECAAYFAlF7D98ACgkQpw8IXSHylJpy0QCgz2LQnk7nQ4hDluLv5WGby+9b
>wU8AoMTP6BFHVDPSemIomzrpcjPcgME9
>=kA9M
>-----END PGP SIGNATURE-----
>___________________________________________________________________________
>Sent via:    Wireshark-announce mailing list <wireshark-announce@xxxxxxxxxxxxx>
>Archives:    http://www.wireshark.org/lists/wireshark-announce
>Unsubscribe: https://wireshark.org/mailman/options/wireshark-announce
>             mailto:wireshark-announce-request@xxxxxxxxxxxxx?subject=unsubscribe