-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I'm proud to announce the release of 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: * 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. 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. * The LOAD() metric in the IO-graph now shows the load in IO units instead of thousands of IO units. 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 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 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. (Bug 1419) The BER dissector might infinitely loop. (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. (Bug 2234) The 64-bit Windows installer does not support Kerberos decryption. (Win64 development page) Application crash when changing real-time option. (Bug 4035) Hex pane display issue after startup. (Bug 4056) Packet list rows are oversized. (Bug 4357) Summary pane selected frame highlighting not maintained. (Bug 4445) Wireshark and TShark will display incorrect delta times in some cases. (Bug 4985) __________________________________________________________ Getting Help Community support is available on 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 the web site. Official Wireshark training and certification are available from Wireshark University. __________________________________________________________ Frequently Asked Questions A complete FAQ is available on the Wireshark web site. __________________________________________________________ Last updated 2013-06-03 10:42:44 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.0.tar.bz2: 27101631 bytes MD5(wireshark-1.10.0.tar.bz2)=72e51cd33fd33c7044a41c2ab51ad7af SHA1(wireshark-1.10.0.tar.bz2)=c78a5d5e589edc8ebc702eb00a284ccbca7721bc RIPEMD160(wireshark-1.10.0.tar.bz2)=924e8d94275c1512b9624d009d69fefa8626b5b2 Wireshark-win32-1.10.0.exe: 22238848 bytes MD5(Wireshark-win32-1.10.0.exe)=32c76e130a7c0746e738bd56f07da3ba SHA1(Wireshark-win32-1.10.0.exe)=f6fad836afe9f44e451773ce617a56165646c202 RIPEMD160(Wireshark-win32-1.10.0.exe)=15887841d1084e2cfc26706a048355bae737fdb8 Wireshark-win64-1.10.0.exe: 28087416 bytes MD5(Wireshark-win64-1.10.0.exe)=7a053d1ef8a133429802f705d574cb58 SHA1(Wireshark-win64-1.10.0.exe)=344192f708ced148705536b49f45a2f325cac814 RIPEMD160(Wireshark-win64-1.10.0.exe)=64ed5c9a91363328ef15d4b101f2b4987e575bcc Wireshark-1.10.0.u3p: 30772650 bytes MD5(Wireshark-1.10.0.u3p)=973cb0abe4a5c3409be5aa623704f4f0 SHA1(Wireshark-1.10.0.u3p)=7b00ba6ee13e528cd65c716a0fb4f27d7c909f3a RIPEMD160(Wireshark-1.10.0.u3p)=76f46ed49fe908ac12e24bd1573c8b2c2fa41b19 WiresharkPortable-1.10.0.paf.exe: 23594648 bytes MD5(WiresharkPortable-1.10.0.paf.exe)=3a2bb29ad8c87366d1bcd210b69941d1 SHA1(WiresharkPortable-1.10.0.paf.exe)=411ebf3c448e7ae79c8de694b2089a8e644c89f3 RIPEMD160(WiresharkPortable-1.10.0.paf.exe)=03e18603bd42c9f0d416162f42f20e0b92b7b49f Wireshark 1.10.0 Intel 64.dmg: 23905721 bytes MD5(Wireshark 1.10.0 Intel 64.dmg)=b49214148e57551a3b6d94eb02d0ee14 SHA1(Wireshark 1.10.0 Intel 64.dmg)=4e7a94ff56f418ca6e25439196efb9f4671687a2 RIPEMD160(Wireshark 1.10.0 Intel 64.dmg)=858db55d405d5bffc2ce8647393d173dd0b4c88e Wireshark 1.10.0 Intel 32.dmg: 21857711 bytes MD5(Wireshark 1.10.0 Intel 32.dmg)=5926c5018617d5d01127b873f7fddb62 SHA1(Wireshark 1.10.0 Intel 32.dmg)=540abecf355e1b35b1b713ed37da4c5d47155b3e RIPEMD160(Wireshark 1.10.0 Intel 32.dmg)=15b43fd47ce8d4b35349106d10e58d59ab574ebe -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.12 (Darwin) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iEYEARECAAYFAlGvlt8ACgkQpw8IXSHylJp9sgCgmW4b0Jpef6aRVLTA0uGjfNpR N+EAni46l6DuXK0K4b0odU31YW/31gQT =ix9P -----END PGP SIGNATURE----- ___________________________________________________________________________ Sent via: Wireshark-announce mailing list <firstname.lastname@example.org> Archives: http://www.wireshark.org/lists/wireshark-announce Unsubscribe: https://wireshark.org/mailman/options/wireshark-announce mailto:wireshark-announce-requ...@wireshark.org?subject=unsubscribe