Wireshark-users: [Wireshark-users] Wireshark 1.8.0rc1 is now available
From: Gerald Combs <gerald@xxxxxxxxxxxxx>
Date: Wed, 06 Jun 2012 12:01:32 -0700
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I'm proud to announce the release of Wireshark 1.8.0rc1. This is the first release candidate for 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 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 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 When saving packets, the default choice is now to save only the displayed packets rather than all packets. 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. Digests wireshark-1.8.0rc1.tar.bz2: 24411907 bytes MD5(wireshark-1.8.0rc1.tar.bz2)=813a0d701759a652ca0c77f478134219 SHA1(wireshark-1.8.0rc1.tar.bz2)=2058756183a3d88e0b698b808e0492de242db88f RIPEMD160(wireshark-1.8.0rc1.tar.bz2)=5e43db25f4490bf2b9e632823afb509ed16427f7 Wireshark-win32-1.8.0rc1.exe: 20905487 bytes MD5(Wireshark-win32-1.8.0rc1.exe)=d6432bc7ea9ea3901b9cbbe9f58a3adc SHA1(Wireshark-win32-1.8.0rc1.exe)=08780a159478ead5161c8a237340a0581306c512 RIPEMD160(Wireshark-win32-1.8.0rc1.exe)=85fc07a944bb2e2418bf0b0946a08444ab8afcc9 Wireshark-win64-1.8.0rc1.exe: 26574607 bytes MD5(Wireshark-win64-1.8.0rc1.exe)=4229a8f6f12b7f33ac96363bcda32e78 SHA1(Wireshark-win64-1.8.0rc1.exe)=75ea39265cd659b8617c6c5e3b1991f656946f67 RIPEMD160(Wireshark-win64-1.8.0rc1.exe)=8eb859852006bbe316bb6a444ba9bedfa4ee7516 Wireshark-1.8.0rc1.u3p: 28305581 bytes MD5(Wireshark-1.8.0rc1.u3p)=b92a28caadba7d6317650ea40abbc77b SHA1(Wireshark-1.8.0rc1.u3p)=ff347b4394d05f474effc2c6e64357a38f550f9b RIPEMD160(Wireshark-1.8.0rc1.u3p)=8b01f708bbec0b55414a115cd521f1c9c0be698c WiresharkPortable-1.8.0rc1.paf.exe: 21933110 bytes MD5(WiresharkPortable-1.8.0rc1.paf.exe)=39c0d5658f93c6785b0c1c678a20e12b SHA1(WiresharkPortable-1.8.0rc1.paf.exe)=bad8f741d43716a4f4d62be41430600add4ce671 RIPEMD160(WiresharkPortable-1.8.0rc1.paf.exe)=7fcd6a7a00bb83543681c6384996f00633ea5c32 Wireshark 1.8.0rc1 Intel 64.dmg: 21770411 bytes MD5(Wireshark 1.8.0rc1 Intel 64.dmg)=a28ba4b4e25f4aee9c557111a9fac1ac SHA1(Wireshark 1.8.0rc1 Intel 64.dmg)=b78c7b35bd0c209dd4942c31a81cd5ed2aeb9772 RIPEMD160(Wireshark 1.8.0rc1 Intel 64.dmg)=f2a1a86e3adc5801ac4ace17032b06755250c367 Wireshark 1.8.0rc1 Intel 32.dmg: 22089476 bytes MD5(Wireshark 1.8.0rc1 Intel 32.dmg)=ce272cbe5348d63d02be66ed24b04b14 SHA1(Wireshark 1.8.0rc1 Intel 32.dmg)=35abbace44d43815e5b9333f9897098e3f5352a5 RIPEMD160(Wireshark 1.8.0rc1 Intel 32.dmg)=6f76df4f481ad0a6848917ee089f8dd7521cfc9b Wireshark 1.8.0rc1 PPC 32.dmg: 22858329 bytes MD5(Wireshark 1.8.0rc1 PPC 32.dmg)=40c5b66ca31cbb7563dedc7f1cc0a657 SHA1(Wireshark 1.8.0rc1 PPC 32.dmg)=1125dc7312e98e20182127cb529f434e7ea5c253 RIPEMD160(Wireshark 1.8.0rc1 PPC 32.dmg)=5c0ead75d456a206a753e97b27b04fcafff6fd07 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk/PqQwACgkQpw8IXSHylJrCdwCeLUogVTOllPypqLrsp8K94ghg KJYAoLBABCD2mCPLbjw3Lltk+535ZVhn =udIa -----END PGP SIGNATURE-----
- Prev by Date: Re: [Wireshark-users] cmdline switch to get absolute sequence numbers?
- Next by Date: [Wireshark-users] SNMP Users Table
- Previous by thread: Re: [Wireshark-users] cmdline switch to get absolute sequence numbers?
- Next by thread: [Wireshark-users] SNMP Users Table
- Index(es):