Wireshark-users: [Wireshark-users] Wireshark 1.7.0 is now available
From: Gerald Combs <gerald@xxxxxxxxxxxxx>
Date: Tue, 08 Nov 2011 16:05:22 -0800
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I'm proud to announce the release of Wireshark 1.7.0. This is an experimental release intended to test features that will go into Wireshark 1.8. 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 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 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.7.0.tar.bz2: 22142779 bytes MD5(wireshark-1.7.0.tar.bz2)=c9f646a15fed6e31c4aa88322b8cce2a SHA1(wireshark-1.7.0.tar.bz2)=e6da826833ece4efa0a257ea8aa8d5c7454dec62 RIPEMD160(wireshark-1.7.0.tar.bz2)=d65be41a4384b1754756b255330cc76e93cdd3af wireshark-win32-1.7.0.exe: 20070828 bytes MD5(wireshark-win32-1.7.0.exe)=87eacb041e180f797350d0717a3aa067 SHA1(wireshark-win32-1.7.0.exe)=3475de84eb7edd0fdc97855f1f5b528fbb779278 RIPEMD160(wireshark-win32-1.7.0.exe)=d793159f8e340f541420f708345cc2e06a930180 wireshark-win64-1.7.0.exe: 25027096 bytes MD5(wireshark-win64-1.7.0.exe)=e3762b5c1b94605f8e6101436331d383 SHA1(wireshark-win64-1.7.0.exe)=5274ed20f4c0da05a1350cdf68e1e9123efa783d RIPEMD160(wireshark-win64-1.7.0.exe)=d41f8b6f771cab738fc6187d1e14741b2c28983a wireshark-1.7.0.u3p: 26912954 bytes MD5(wireshark-1.7.0.u3p)=9bcf5a5dccf31d447ce3dc0ebeb57a35 SHA1(wireshark-1.7.0.u3p)=09c11d6f88bd7cf282b6682f5bd7a52b987281f9 RIPEMD160(wireshark-1.7.0.u3p)=4e544664a0c17c9cf672088841bc1edafe4b78f1 WiresharkPortable-1.7.0.paf.exe: 21053445 bytes MD5(WiresharkPortable-1.7.0.paf.exe)=92c7284c7904d8fc6ac990b7fa8367b1 SHA1(WiresharkPortable-1.7.0.paf.exe)=3aaa1fc0ac313e930345510e0616ddaea4686ac8 RIPEMD160(WiresharkPortable-1.7.0.paf.exe)=eb034aebbc5f59faf257f8a9ba71240b15ee6356 Wireshark 1.7.0 Intel 32.dmg: 21079754 bytes MD5(Wireshark 1.7.0 Intel 32.dmg)=f29288c35a978f2330316beaa3605d79 SHA1(Wireshark 1.7.0 Intel 32.dmg)=adbdefa6f4435c007066f0563b8ceeaa517b446a RIPEMD160(Wireshark 1.7.0 Intel 32.dmg)=9f5aacb465161b3fb1372392f5129c3a58b2d14d Wireshark 1.7.0 Intel 64.dmg: 20868155 bytes MD5(Wireshark 1.7.0 Intel 64.dmg)=8d7b091ccdffcf42fdb4daba89378ae1 SHA1(Wireshark 1.7.0 Intel 64.dmg)=7501e02934cad6a6590db4fe4d07b87e11c5ed00 RIPEMD160(Wireshark 1.7.0 Intel 64.dmg)=f82e40b92e88adea153dd4b833281d9eead67aa4 Wireshark 1.7.0 PPC 32.dmg: 21825249 bytes MD5(Wireshark 1.7.0 PPC 32.dmg)=4ab184e2f938d2ce48be96a1069c4ee4 SHA1(Wireshark 1.7.0 PPC 32.dmg)=294dcc7d2b9b803a7960352fe9d09194a3b6e20c RIPEMD160(Wireshark 1.7.0 PPC 32.dmg)=2a2fd6ab2305568c8d8446384a308a8da9a29395 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk65w8IACgkQpw8IXSHylJqxuACeJy7e4JDTE9r4P8lmcbAY3r8Z bb8AoLqWQTw+yKvzLysB/6BUBOeNfZaR =3sKL -----END PGP SIGNATURE-----
- Prev by Date: Re: [Wireshark-users] Request for PDCP pcap
- Next by Date: Re: [Wireshark-users] RTCP: Filtering SDES items in 'tshark'
- Previous by thread: Re: [Wireshark-users] BitTorrent info_hash decoder using Wireshark
- Next by thread: [Wireshark-users] How to parse incoming DNS responses but do not query DNS server
- Index(es):