Wireshark-announce: [Wireshark-announce] Wireshark 1.8.0 is now available
Date Prev Thread Prev
From: Wireshark announcements <[email protected]>
Date: Thu, 21 Jun 2012 14:15:39 -0700
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

I'm proud to announce the release of Wireshark 1.8.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:

     o When saving the displayed packets, packets which are
       dependencies (e.g., due to reassembly) of the displayed
       packets are included in the list of saved packets (Bug 3315).

     o Rearranging columns in preferences doesn't work on 64-bit
       Windows. (Bug 6077)

  New and Updated Features

   The following features are new (or have been significantly
   updated) since version 1.6:

     o Wireshark supports capturing from multiple interfaces at once.

     o You can now add, edit, and save packet and capture file
       annotations.

     o Wireshark, TShark, and their associated utilities now save
       files using the pcap-ng file format by default. (Your copy of
       Wireshark might still use the pcap file format if pcap-ng is
       disabled in your preferences.)

     o Decryption key management for IEEE 802.11, IPsec, and ISAKMP
       is easier.

     o OID resolution is now supported on 64-bit Windows.

     o The "Save As" menu item has been split into "Save As", which
       lets you save a file using a different filename and "Export
       Specified Packets", which lets you have more control over
       which packets are saved.

     o TCP fast retransmissions are now indicated as an expert info
       note, rather than a warning, just as TCP retransmissions are.

     o TCP window updates are no longer colorized as "Bad TCP".

     o TShark's command-line options have changed. The previously
       undocumented -P option is now -2 option for performing a
       two-pass analysis; the former -S option is now the -P option
       for printing packets even if writing to a file, and the -S
       option is now used to specify a different line separator
       between packets.

     o GeoIP IPv6 databases are now supported.

  New Protocol Support

   Aastra Signalling Protocol (AASP), ActiveMQ OpenWire, Bandwidth
   Reservation Protocol (BRP), Bazaar, Binary Floor Control Protocol,
   BitTorrent DHT, C12.22, CANopen, CIP Motion, CIP Safety, Cisco
   FabricPath MiM, DMX Channel Data, DMX SIP, DMX Test, DMX Text,
   DMX, DVB Application Information Table, DVB Bouquet Association
   Table, DVB Event Information Table, DVB MultiProtocol
   Encapsulation (DVB-MPE), DVB Network Information Table, DVB
   Service Description Table, DVB Time and Date Table, DVB Time
   Offset Table, DVB/ETSI IP Data Cast (IPDC) Electronic Service
   Guide (ESG), ECP VDP, EIA-709.1 (LonTalk), EIA-852 (CN/IP), ELCOM,
   Ericsson A-bis OML (OM 2000), Ericsson HDLC, Ericsson Proprietary
   PCAP, ETSI CAT, ETV-AM Data, ETV-AM EISS Section, Flight Message
   Transfer Protocol (FMTP), Gadu-Gadu, GEO-Mobile Radio (1) BCCH,
   GEO-Mobile Radio (1) Common, GEO-Mobile Radio (1) DTAP, GEO-Mobile
   Radio (1) Radio Resource, Gluster Callback, Gluster CLI, Gluster
   Dump, Gluster Portmap, GlusterD, GlusterFS Callback, GlusterFS
   Handshake, GlusterFS, GSM A-bis OML, GSM CBCH, GSM Cell Broadcast
   Service, GSM SIM, H.248.2, Hadoop Distributed File System (HDFS),
   HART/IP, Hazelcast, HDFS Data, High bandwidth Digital Content
   Protection (HDCP), High-availability Seamless Redundancy (HSR),
   HomePlug AV, HSR/PRP, IEEE 1722.1, ISO 7816, ixveriwave, Kismet
   drone/server protocol, KristalliNet, LCS-AP, Link Access
   Procedure, Satellite channel (LAPSat), LLRP, LTE Positioning
   Protocol A (LPPa), LTE Positioning Protocol, M3 Application
   Protocol (M3AP), MAC Address Acquisition Protocol, MBMS
   synchronisation protocol, Microsoft Credential Security Support
   Provider (CredSSP), MoldUDP, MoldUDP64, MPEG Conditional Access,
   MPEG descriptors, MPEG DSM-CC, MPEG Program Association Table
   (PAT), MPEG Program Map Table, MPEG Section, MPLS Packet Loss and
   Delay Measurement, MPLS-TP Protection State Coordination, Multiple
   VLAN Registration Protocol (MRVP), Netfilter LOG, NOE, NXP MiFare,
   NXP PN532, Open IPTV Forum openSAFETY, Performance Co-Pilot (PCP),
   PPI Sensor, RDP, RTP-MIDI, SBc Application Part (SBc-AP),
   SDH/SONET, Solaris IP over InfiniBand, Sony FeliCa, T.124, UA
   (Universal Alcatel), UA3G, UASIP, UAUDP, USB Integrated Circuit
   Card Interface Device Class (CCID), V5 Data Link Layer (V5DL), V5
   Envelope Function (V5EF), Virtual eXtensible Local Area Network
   (VXLAN), VSS-Monitoring, Vuze DHT, WaveAgent, WebSocket, WSE
   Remote Ethernet, XMCP, YAMI

  Updated Protocol Support

   Too many protocols have been updated to list here.

  New and Updated Capture File Support

   Aethra Telecommunications' PC108, Catapult DCT2000, Citrix
   NetScaler, Cisco Secure IDS IPLog, Endace ERF, Gammu DCT3, Generic
   MIME, IBM iSeries, InfoVista 5View, Ixia IxVeriWave, LANalyzer,
   Microsoft NetMon, MPEG2-TS, Network Instruments Observer, Nokia
   DCT3, pcap, pcap-ng, Solaris snoop, TamoSoft CommView, Tektronix
   K12xx, XML

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.
   (Bug 1814)

   Filtering tshark captures with display 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.


Digests

wireshark-1.8.0.tar.bz2: 24425043 bytes
MD5(wireshark-1.8.0.tar.bz2)=3eca81253800a0089d0f957e75853b05
SHA1(wireshark-1.8.0.tar.bz2)=d45b2828fc6dfac697f752f146e6cf43f4776047
RIPEMD160(wireshark-1.8.0.tar.bz2)=944f2ef662fc432ce0ab22f9efd9195366fc1763

Wireshark-win32-1.8.0.exe: 20912453 bytes
MD5(Wireshark-win32-1.8.0.exe)=1e791b80e0693e174c6666930b0728a9
SHA1(Wireshark-win32-1.8.0.exe)=86a8b46131107e5a6f776e71720987601ac30f8b
RIPEMD160(Wireshark-win32-1.8.0.exe)=107670574e31d516913fadd1be6bf01bb0a29dcf

Wireshark-win64-1.8.0.exe: 26586887 bytes
MD5(Wireshark-win64-1.8.0.exe)=f4af66f8654c8c9cdee33f5e53cccd7a
SHA1(Wireshark-win64-1.8.0.exe)=5813b3e271f1a384025dcc668aff951fd2a44079
RIPEMD160(Wireshark-win64-1.8.0.exe)=06afb6dda4820f29f331eb6ee31288e439931c9d

Wireshark-1.8.0.u3p: 28304605 bytes
MD5(Wireshark-1.8.0.u3p)=6845ebd34214d949b689b430b7df49f2
SHA1(Wireshark-1.8.0.u3p)=f584e077d59ba319c7b51252f097f44e07f1a40a
RIPEMD160(Wireshark-1.8.0.u3p)=a19ecafac4404a6246ab2a81d21c5150cdc9c771

WiresharkPortable-1.8.0.paf.exe: 21936447 bytes
MD5(WiresharkPortable-1.8.0.paf.exe)=d24f627c35c9a5e989c67b615f90f4f9
SHA1(WiresharkPortable-1.8.0.paf.exe)=f2c8789423ef90ba4b4f168fe2da1c90faaa62c6
RIPEMD160(WiresharkPortable-1.8.0.paf.exe)=2a80a4a3273e2ba249ea5906786edf39c834a80e

Wireshark 1.8.0 Intel 64.dmg: 21751295 bytes
MD5(Wireshark 1.8.0 Intel 64.dmg)=a374ef78040e9fc0aa8d915d9fffa67b
SHA1(Wireshark 1.8.0 Intel
64.dmg)=246cd331ca2340bc0c09f4fc362d2b7cba7e941c
RIPEMD160(Wireshark 1.8.0 Intel
64.dmg)=deca3031880550bbb9dee78dfe87ec6893ea421b

Wireshark 1.8.0 Intel 32.dmg: 22072614 bytes
MD5(Wireshark 1.8.0 Intel 32.dmg)=364b6314c78c14b95f507ba5b2a6eedd
SHA1(Wireshark 1.8.0 Intel
32.dmg)=50c3a430c369626261a3fb7c9203baaa00cfb314
RIPEMD160(Wireshark 1.8.0 Intel
32.dmg)=ded63745be4548de3e60e215c18ed38587b7d53a

Wireshark 1.8.0 PPC 32.dmg: 22848679 bytes
MD5(Wireshark 1.8.0 PPC 32.dmg)=c17bb8191435f2ee3849cc75d20a6f7e
SHA1(Wireshark 1.8.0 PPC 32.dmg)=a3f24904d226eea6ee7c74e2b878c59e77793cb9
RIPEMD160(Wireshark 1.8.0 PPC
32.dmg)=7aa470c0ad315eec55cc1adb1fc165f199ea0bdf
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (Darwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAk/jjvsACgkQpw8IXSHylJrpzQCgm3XTBqsY3XJz1xs8D9hpFdeF
L5MAoMcA1dhPItLcvIKo3j6JFkjU5paO
=LDqG
-----END PGP SIGNATURE-----