[Gerald Combs <gerald@xxxxxxxxxxxxx>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

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

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-11

       The PPP dissector could crash. (Debian bug 680056)

       Versions affected: 1.4.0 to 1.4.13, 1.6.0 to 1.6.8, 1.8.0.

       CVE-2012-4048

     o wnpa-sec-2012-12

       The NFS dissector could use excessive amounts of CPU. (Bug
       7436)

       Versions affected: 1.4.0 to 1.4.13, 1.6.0 to 1.6.8, 1.8.0.

       CVE-2012-4049

   The following bugs have been fixed:

     o Cannot run tshark under tcp using decode-as format for syslog.
       (Bug 5241)

     o Problem with Floating point (double-precision). (Bug 6917)

     o Netscreen - can't parse packet-header. (Bug 7340)

     o Wireshark fails to link because of missing @GLIB_LIBS@
       reference in Makefile.am. (Bug 7427)

  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

   DIAMETER, NFS, PPP, SNMP, Syslog, UDP-Lite, VMLAB

  New and Updated Capture File Support

   Juniper NetScreen

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

   Wireshark might make your system disassociate from a wireless
   network on OS X 10.4. (Bug 1315)

   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 ship with the same libraries
   as the 32-bit installer. (Bug 3610)

   Hex pane display issue after startup. (Bug 4056)

   Packet list rows are oversized. (Bug 4357)

   Summary pane selected frame highlighting not maintained. (Bug
   4445)

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.4.14.tar.bz2: 21180244 bytes
MD5(wireshark-1.4.14.tar.bz2)=89ca87158a1cb8d852770a41c5488fd3
SHA1(wireshark-1.4.14.tar.bz2)=dda2445838f977e3c3c64babd94c72fb60987d74
RIPEMD160(wireshark-1.4.14.tar.bz2)=d95f082fbb6336d9037df2debe8eaf20f9dc04ad

wireshark-win32-1.4.14.exe: 19859703 bytes
MD5(wireshark-win32-1.4.14.exe)=3a2878fb5a77ac219522ad9d70505731
SHA1(wireshark-win32-1.4.14.exe)=bed9ba22ffa0e9ad828ac061e670e9aef1bf5de3
RIPEMD160(wireshark-win32-1.4.14.exe)=05f61042a94af56f5b14381e0d8e4dd794303d76

wireshark-win64-1.4.14.exe: 21884095 bytes
MD5(wireshark-win64-1.4.14.exe)=40d18fa26420079fec3b71aa891c2c0b
SHA1(wireshark-win64-1.4.14.exe)=2ea2a3f025124fe0719e96f44179cb7931dc0a8c
RIPEMD160(wireshark-win64-1.4.14.exe)=3a1430d30a19affb097eea72c201e569cc4ee656

wireshark-1.4.14.u3p: 26407969 bytes
MD5(wireshark-1.4.14.u3p)=e919fd1fbdeecf79a101f4374e806925
SHA1(wireshark-1.4.14.u3p)=fe1573ad69a220057ac503b539184aa00b41474c
RIPEMD160(wireshark-1.4.14.u3p)=c071fca548f6de37db6ac6b2529d14f1e0c35e38

WiresharkPortable-1.4.14.paf.exe: 20674688 bytes
MD5(WiresharkPortable-1.4.14.paf.exe)=000dd23b1d94fbcb0a417f2c51d5d020
SHA1(WiresharkPortable-1.4.14.paf.exe)=0336b170d0e5458b2c8c10b7499b7e4b22ecb726
RIPEMD160(WiresharkPortable-1.4.14.paf.exe)=01df3422af78c45c4e072eeb3be28f8bec55dd6f

Wireshark 1.4.14 Intel 32.dmg: 47957946 bytes
MD5(Wireshark 1.4.14 Intel 32.dmg)=c24ce226024404ea220602f5d5e43e94
SHA1(Wireshark 1.4.14 Intel
32.dmg)=0234212251d57a4c3ee35a674178ffee1a69b3a4
RIPEMD160(Wireshark 1.4.14 Intel
32.dmg)=eade6006b255867e123330419b159281e752eafb

Wireshark 1.4.14 Intel 64.dmg: 45646809 bytes
MD5(Wireshark 1.4.14 Intel 64.dmg)=3cb8bedc144c113b3d8cb46427244de0
SHA1(Wireshark 1.4.14 Intel
64.dmg)=81e38ece439af753830e6760799e259b7aa607cf
RIPEMD160(Wireshark 1.4.14 Intel
64.dmg)=a21274a6c7faa1d90365615ad16a3d6c7aaffb3f

Wireshark 1.4.14 PPC 32.dmg: 50518380 bytes
MD5(Wireshark 1.4.14 PPC 32.dmg)=72e31d10b9882be62aed9a458b678200
SHA1(Wireshark 1.4.14 PPC 32.dmg)=c2b8fb4074f3e2c5c8290080c2e17e8b7b766be2
RIPEMD160(Wireshark 1.4.14 PPC
32.dmg)=5627a1d6f453e8774cf72c4599df879f4b9918d5

patch-wireshark-1.4.13-to-1.4.14.diff.bz2: 130563 bytes
MD5(patch-wireshark-1.4.13-to-1.4.14.diff.bz2)=9b9fb48b4dadbc71c61444d2f87abf91
SHA1(patch-wireshark-1.4.13-to-1.4.14.diff.bz2)=9a380d22543fb3df73bfc9114d68fe8089ef75f0
RIPEMD160(patch-wireshark-1.4.13-to-1.4.14.diff.bz2)=5e9fedeed99057be74aa09d1dc2a24a8eb2fab48
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (Darwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAlAPBMgACgkQpw8IXSHylJpcpACfVQUn3A8iNaKgUdKZFQ9eqZUv
OhMAn2sv3bqFpzrfZ2N/BHDy7B1frhqx
=1aok
-----END PGP SIGNATURE-----