Wireshark-users: Re: [Wireshark-users] [Wireshark-announce] Wireshark 1.8.2 is now available
From: Marco Zuppone <msz@xxxxxx>
Date: Thu, 16 Aug 2012 17:23:02 +0100
Hello,

first of all the even versions (1.4, 1.6, 1.8) are all stable.
Why the old stable branches are still maintained ?
This is due to the fact (I think) the different versions have different hardware/software requirements and so if you need to work with an old software/hardware for some legacy reason you still have access to these versions.
Regards,
Marco Zuppone
On 16 Aug 2012, at 02:10, Jim LeJeune <jlejeune426@xxxxxxxxx> wrote:

Could you please tell me why you are "releasing" Wireshark 1.4.15, 1.6.10, AND 1.8.2 ??? !!!

On Wed, Aug 15, 2012 at 3:20 PM, Wireshark announcements <wireshark-announce@xxxxxxxxxxxxx> wrote:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

I'm proud to announce the release of Wireshark 1.8.2.

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 vulnerabilities have been fixed.

     o wnpa-sec-2012-13

       The DCP ETSI dissector could trigger a zero division. Reported
       by Laurent Butti. (Bug 7566)

       Versions affected: 1.4.0 to 1.4.14, 1.6.0 to 1.6.9, 1.8.0 to
       1.8.1.

       CVE-2012-4285

     o wnpa-sec-2012-14

       The MongoDB dissector could go into a large loop. Reported by
       Ben Schmidt. (Bug 7572)

       Versions affected: 1.8.0 to 1.8.1.

       CVE-2012-4287

     o wnpa-sec-2012-15

       The XTP dissector could go into an infinite loop. Reported by
       Ben Schmidt. (Bug 7571)

       Versions affected: 1.4.0 to 1.4.14, 1.6.0 to 1.6.9, 1.8.0 to
       1.8.1.

       CVE-2012-4288

     o wnpa-sec-2012-16

       The ERF dissector could overflow a buffer. Reported by Laurent
       Butti. (Bug 7563)

       Versions affected: 1.8.0 to 1.8.1.

       CVE-2012-4294 CVE-2012-4295

     o wnpa-sec-2012-17

       The AFP dissector could go into a large loop. Reported by
       Stefan Cornelius. (Bug 7603)

       Versions affected: 1.4.0 to 1.4.14, 1.6.0 to 1.6.9, 1.8.0 to
       1.8.1.

       CVE-2012-4289

     o wnpa-sec-2012-18

       The RTPS2 dissector could overflow a buffer. Reported by
       Laurent Butti. (Bug 7568)

       Versions affected: 1.4.0 to 1.4.14, 1.6.0 to 1.6.9, 1.8.0 to
       1.8.1.

       CVE-2012-4296

     o wnpa-sec-2012-19

       The GSM RLC MAC dissector could overflow a buffer. Reported by
       Laurent Butti. (Bug 7561)

       Versions affected: 1.6.0 to 1.6.9, 1.8.0 to 1.8.1.

       CVE-2012-4297

     o wnpa-sec-2012-20

       The CIP dissector could exhaust system memory. Reported by Ben
       Schmidt. (Bug 7570)

       Versions affected: 1.4.0 to 1.4.14, 1.6.0 to 1.6.9, 1.8.0 to
       1.8.1.

       CVE-2012-4291

     o wnpa-sec-2012-21

       The STUN dissector could crash. Reported by Laurent Butti.
       (Bug 7569)

       Versions affected: 1.4.0 to 1.4.14, 1.6.0 to 1.6.9, 1.8.0 to
       1.8.1.

       CVE-2012-4292

     o wnpa-sec-2012-22

       The EtherCAT Mailbox dissector could abort. Reported by
       Laurent Butti. (Bug 7562)

       Versions affected: 1.4.0 to 1.4.14, 1.6.0 to 1.6.9, 1.8.0 to
       1.8.1.

       CVE-2012-4293

     o wnpa-sec-2012-23

       The CTDB dissector could go into a large loop. Reported by Ben
       Schmidt. (Bug 7573)

       Versions affected: 1.4.0 to 1.4.14, 1.6.0 to 1.6.9, 1.8.0 to
       1.8.1.

       CVE-2012-4290

     o wnpa-sec-2012-24

       The pcap-ng file parser could trigger a zero division. (Bug
       7533)

       Versions affected: 1.8.0 to 1.8.1.

       CVE-2012-4286

     o wnpa-sec-2012-25

       The Ixia IxVeriWave file parser could overflow a buffer. (Bug
       7533)

       Versions affected: 1.8.0 to 1.8.1.

       CVE-2012-4298

   The following bugs have been fixed:

     o Move Y.1711 out of MPLS dissector. (Bug 6787)

     o Patch: Add frame.interface_id support for ERF file format.
       (Bug 7266)

     o Freeze when Resizing or Moving while capturing. (Bug 7305)

     o Wireshark crashes when using multiple files. (Bug 7423)

     o Wireshark crashes on opening very short NFS pcap file. (Bug
       7498)

     o Analyze->Apply as Filter and Analyze->Prepare a Filter cause
       crashes. (Bug 7506)

     o crashes in interface list, pipe handling. (Bug 7511)

     o ISDN LAPD X.31 packet traffic can not be decoded. (Bug 7514)

     o GIOP request_id used for sub dissectors is not assigned when
       decoding GIOP 1.2 Request message. (Bug 7516)

     o pcap-ng -ISB always writes 0 for isb_ifrecv option. (Bug 7523)

     o GSM classmark3 decode wrong. (Bug 7524)

     o mem corruption\heap corruption\div0 bugs. (Bug 7533)

     o DNS AD flag not shown properly. (Bug 7555)

     o Wireshark and TShark crash at start with invalid color filter
       on SPARC. (Bug 7634)

  New and Updated Features

   There are no new features in this release.

  New Protocol Support

   There are no new protocols in this release.

  Updated Protocol Support

   AFP, Apache JServ Protocol v1.3, Bluetooth L2CAP, CIP, CTDB, DCP
   ETSI, ERF, EtherCAT Mailbox, FC Link Control, GIOP, GSM A, GSM RLC
   MAC, GTP, GTPv2, ISDN, LISP, MongoDB, MPLS ITU-T Y.1711 OAM, MPLS
   PM, NFS, RTPS2, SCTP, STUN, XTP

  New and Updated Capture File Support

   Ixia IxVeriWave, pcap-ng

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.2.tar.bz2: 24121798 bytes
MD5(wireshark-1.8.2.tar.bz2)=5e3ea7eed50dace479e12f49d24506f4
SHA1(wireshark-1.8.2.tar.bz2)=4737d9745dbf002444ea42615243abf3bb80b943
RIPEMD160(wireshark-1.8.2.tar.bz2)=5fece857d5187b146a690fda111a0611e108c2a9

Wireshark-win32-1.8.2.exe: 20952624 bytes
MD5(Wireshark-win32-1.8.2.exe)=5b21cb547e53d762d56733293fcb1443
SHA1(Wireshark-win32-1.8.2.exe)=e619813a658f0ea522cf67259276a45d68c25698
RIPEMD160(Wireshark-win32-1.8.2.exe)=0a79f676847d260efda736602fdd6a74b7dceb97

Wireshark-win64-1.8.2.exe: 26624472 bytes
MD5(Wireshark-win64-1.8.2.exe)=5f604647f30b3c9e9604d0edaceaf21a
SHA1(Wireshark-win64-1.8.2.exe)=c12d8d3b954c26df0a2b34ae85810223734c344d
RIPEMD160(Wireshark-win64-1.8.2.exe)=6756d7cc9a68a548fab968f69bc3897b76c17084

Wireshark-1.8.2.u3p: 28364992 bytes
MD5(Wireshark-1.8.2.u3p)=1de4fa4364e92f6f986c9998bc8aa34f
SHA1(Wireshark-1.8.2.u3p)=a4d2d7a82e5ee581f0d5a8bf937bfe65d68bbb60
RIPEMD160(Wireshark-1.8.2.u3p)=4663cf7f1047b0b71f15f6a98f0aeee8d5100c78

WiresharkPortable-1.8.2.paf.exe: 21965928 bytes
MD5(WiresharkPortable-1.8.2.paf.exe)=6a1b8bc92db4ed47ea1e42bbf1134ec2
SHA1(WiresharkPortable-1.8.2.paf.exe)=36e46b955d757950f6088cff058c0d8353c77f23
RIPEMD160(WiresharkPortable-1.8.2.paf.exe)=ca6ff5364cefccc40175f91306a5b13389b20393

Wireshark 1.8.2 Intel 32.dmg: 22056362 bytes
MD5(Wireshark 1.8.2 Intel 32.dmg)=7891af48ebfdb5b722eae70d652c016d
SHA1(Wireshark 1.8.2 Intel
32.dmg)=c3743c5f74554ba52b212ffa1cb9a5843a8818ee
RIPEMD160(Wireshark 1.8.2 Intel
32.dmg)=951628019771b274291b30cf0a3e830664c8afb0

Wireshark 1.8.2 Intel 64.dmg: 21744672 bytes
MD5(Wireshark 1.8.2 Intel 64.dmg)=24a842d1d1be59f60cbe13c344031823
SHA1(Wireshark 1.8.2 Intel
64.dmg)=5044639e002857d339e0a1f0da3ac7066f521aa2
RIPEMD160(Wireshark 1.8.2 Intel
64.dmg)=ae25d382e5259a6805c96abc0bae1aef1a5a29c0

Wireshark 1.8.2 PPC 32.dmg: 22870644 bytes
MD5(Wireshark 1.8.2 PPC 32.dmg)=ce6058b1a9ee6a00841b2ef0ab19ab62
SHA1(Wireshark 1.8.2 PPC 32.dmg)=7eccc8237828df02d9ad351e290967d6b2015889
RIPEMD160(Wireshark 1.8.2 PPC
32.dmg)=27b60ad605dbf0e8728a60baddb385aace8585e9

patch-wireshark-1.8.1-to-1.8.2.diff.bz2: 73250 bytes
MD5(patch-wireshark-1.8.1-to-1.8.2.diff.bz2)=ea35b096d9e7944390a8c942d1138c90
SHA1(patch-wireshark-1.8.1-to-1.8.2.diff.bz2)=8cc87bb223a2273faaf200cc9f410373e02409c4
RIPEMD160(patch-wireshark-1.8.1-to-1.8.2.diff.bz2)=97dcef9418399ff8f97b7fa61c0b09020bfe0823
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (Darwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAlAsBJEACgkQpw8IXSHylJrunACfedscW6/0Dvjo+AJff2lVmhUJ
CZYAn0Czuiob1hiJttDoa5EBaLeXHxjN
=5xii
-----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

___________________________________________________________________________
Sent via:    Wireshark-users mailing list <wireshark-users@xxxxxxxxxxxxx>
Archives:    http://www.wireshark.org/lists/wireshark-users
Unsubscribe: https://wireshark.org/mailman/options/wireshark-users
            mailto:wireshark-users-request@xxxxxxxxxxxxx?subject=unsubscribe