wireshark-dev November 2011 archive
Main Archive Page > Month Archives  > wireshark-dev archives
wireshark-dev: Re: [Wireshark-dev] Wireshark 1.4.10 is now avail

Re: [Wireshark-dev] Wireshark 1.4.10 is now available

From: Krishnamurthy Mayya <krishnamurthymayya_at_nospam>
Date: Tue Nov 01 2011 - 19:59:39 GMT
To: Developer support list for Wireshark <wireshark-dev@wireshark.org>

Hi all,
 A small doubt here. Is the wireshark stable version available now
i.e.(wireshark-1.4.9) is the one which has been renamed from 1.4.6 ?????? I
am trying to get the source code of 1.4.6 but not able to get it.
 And one more question is, we are developing extensions for wireshark and
currently with version 1.4.9 we have been successful in doing so. Would it
be more appropriate if we take the development version 1.7.x and submit our
changes OR as long as the source is clearly mentioned any version would do??

Thanks and regards
Nikitha Malgi
Krishnamurthy Mayya
(IP Infusion Software India , Bangalore )

On Wed, Nov 2, 2011 at 1:14 AM, Gerald Combs <gerald@wireshark.org> wrote:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> I'm proud to announce the release of Wireshark 1.4.10.
>
> 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-2011-18
>
> Huzaifa Sidhpurwala of Red Hat Security Response Team
> discovered that the Infiniband dissector could dereference a
> NULL pointer. (Bug 6476)
>
> Versions affected: 1.4.0 to 1.4.9, 1.6.0 to 1.6.2.
>
> o wnpa-sec-2011-19
>
> Huzaifa Sidhpurwala of Red Hat Security Response Team
> discovered a buffer overflow in the ERF file reader. (Bug
> 6479)
>
> Versions affected: 1.4.0 to 1.4.9, 1.6.0 to 1.6.2.
>
> The following bugs have been fixed:
>
> o Assertion failed when doing File->Quit->Save during live
> capture. (Bug 1710)
>
> o Wrong PCEP XRO sub-object decoding. (Bug 3778)
>
> o Decoding [Status Records] Timestamp Sequence Field in Bundle
> Protocol fails if over 32 bits. (Bug 4109)
>
> o wireshark-1.4.2 crashes when testing the example python
> dissector because of a dissector count assertion. (Bug 5431)
>
> o Wireshark crashes when attempting to open a file via drag &
> drop when there's already a file open. (Bug 5987)
>
> o Add the ability to save filters from the Filter Toolbar into
> buttons on the Filter Toolbar. (Bug 6207)
>
> o Adding and removing custom HTTP headers requires a restart.
> (Bug 6241)
>
> o Can't read full 64-bit SNMP values. (Bug 6295)
>
> o BACnet property time-synchronization-interval (204) name shown
> incorrectly as time-synchronization-recipients. (Bug 6336)
>
> o [ASN.1 PER] Incorrect decoding of BIT STRING type. (Bug 6347)
>
> o Export -> Object -> HTTP -> save all: Error on saving files.
> (Bug 6362)
>
> o Incorrect identification of UDP-encapsulated NAT-keepalive
> packets. (Bug 6414)
>
> o S1AP protocol can't decode IPv6 transportLayerAddress. (Bug
> 6435)
>
> o RTPS2 dissector doesn't handle 0 in the octestToNextHeader
> field. (Bug 6449)
>
> o packet-ajp13 fix, cleanup, and enhancement. (Bug 6452)
>
> o Network Instruments Observer file format bugs. (Bug 6453)
>
> o Wireshark crashes when using "Open Recent" 2 times in a row.
> (Bug 6457)
>
> o Wireshark packet_gsm-sms, display bug: Filler bits in TP-User
> Data Header. (Bug 6469)
>
> o wireshark unable to decode NetFlow options which have system
> scope size != 4 bytes. (Bug 6471)
>
> o Display filter Expression Dialog Box Error. (Bug 6472)
>
> 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
>
> AJP13, ASN.1 PER, BACapp, DTN, GSM SMS, Infiniband, IPsec,
> NetFlow, PCEP, RTPS2,
>
> New and Updated Capture File Support
>
> .
>
> 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.
>
> Training is available from Wireshark University.
>
> Frequently Asked Questions
>
> A complete FAQ is available on the Wireshark web site.
>
>
>
> Digests
>
> wireshark-1.4.10.tar.bz2: 20611930 bytes
> MD5(wireshark-1.4.10.tar.bz2) =
> d688 827a 9b99 083f d995 2c4f c0f3 410c
> SHA1(wireshark-1.4.10.tar.bz2) =
> ae7c 560c bb8f 87d4 64ec f56b a4d7 2f1c d542 f3a6
> RIPEMD160(wireshark-1.4.10.tar.bz2) =
> c84f 56ca b1ca 5e08 bf02 30c0 6aad 726c d49e df9d
>
> wireshark-win32-1.4.10.exe: 19794589 bytes
> MD5(wireshark-win32-1.4.10.exe) =
> 0fae c58c 84c4 7b79 2897 044e c2fc 1e07
> SHA1(wireshark-win32-1.4.10.exe) =
> 34df 8056 527d 49f4 7d57 8f03 3caf aca4 12f3 d628
> RIPEMD160(wireshark-win32-1.4.10.exe) =
> 18c7 cbf4 98f4 81c6 ee0f 5920 4577 3335 f9d2 4cdf
>
> wireshark-win64-1.4.10.exe: 21858019 bytes
> MD5(wireshark-win64-1.4.10.exe) =
> 4092 afa3 9c8e 1ed1 749e d072 f6d8 dbac
> SHA1(wireshark-win64-1.4.10.exe) =
> c476 89f1 c98b 9e8e 16cb 9e10 bba7 b681 5646 85d5
> RIPEMD160(wireshark-win64-1.4.10.exe) =
> 9dae 9a29 e213 6678 51b1 7e19 9820 d34d e8cf 8264
>
> wireshark-1.4.10.u3p: 26296136 bytes
> MD5(wireshark-1.4.10.u3p) =
> 27d0 03e8 7b2b 33c8 36c1 c822 cde7 824d
> SHA1(wireshark-1.4.10.u3p) =
> e609 b0ba 0c1e e3ac 1f04 a0d9 ff8e 04f2 ae8a 5b83
> RIPEMD160(wireshark-1.4.10.u3p) =
> f831 cf8a b356 44f4 745f 1ba1 a05c b4e4 2a03 9e5f
>
> WiresharkPortable-1.4.10.paf.exe: 20606108 bytes
> MD5(WiresharkPortable-1.4.10.paf.exe) =
> 9062 2b1c ff19 04b4 06e7 a1bd e5d2 2fb9
> SHA1(WiresharkPortable-1.4.10.paf.exe) =
> 0417 f786 d9ff 1002 9efc 35ff 5f2e 5486 a1fc 1826
> RIPEMD160(WiresharkPortable-1.4.10.paf.exe) =
> dba0 b226 481f c479 872b 6ed5 a0ca 2d57 a7b2 628e
>
> Wireshark 1.4.10 Intel 32.dmg: 47808846 bytes
> MD5(Wireshark 1.4.10 Intel 32.dmg) =
> 4dce 42ec d865 aa76 da6e f3b4 b51c 148f
> SHA1(Wireshark 1.4.10 Intel 32.dmg) =
> 00b9 506e c11f 27eb 437b ab01 7097 b3b8 438b 82ce
> RIPEMD160(Wireshark 1.4.10 Intel 32.dmg) =
> 4953 47e0 6d09 c028 f360 d9bb 43c8 9915 158b f31f
>
> Wireshark 1.4.10 Intel 64.dmg: 45529934 bytes
> MD5(Wireshark 1.4.10 Intel 64.dmg) =
> b9e9 bd29 4126 bc9a 2194 db95 b30e c9d7
> SHA1(Wireshark 1.4.10 Intel 64.dmg) =
> 6e46 567f 0cd6 2741 a161 ba0c f816 c23a 91c7 2a85
> RIPEMD160(Wireshark 1.4.10 Intel 64.dmg) =
> 10e7 1908 9270 72b5 98ad 6234 4d3f 9175 27cc 2b7f
>
> Wireshark 1.4.10 PPC 32.dmg: 50352432 bytes
> MD5(Wireshark 1.4.10 PPC 32.dmg) =
> 46a4 31cf 6a93 a5fd 2839 c659 57fe 5c97
> SHA1(Wireshark 1.4.10 PPC 32.dmg) =
> dd6a 3552 ebe3 9511 e9b2 40a7 bb5d 2302 d38a f422
> RIPEMD160(Wireshark 1.4.10 PPC 32.dmg) =
> 0e21 8bef 7147 e7d6 40d0 b52e 3416 ffef 92cd f107
>
> patch-wireshark-1.4.9-to-1.4.10.diff.bz2: 865147 bytes
> MD5(patch-wireshark-1.4.9-to-1.4.10.diff.bz2) =
> f98a 0b02 a85a d42a 1a59 b409 243a fe48
> SHA1(patch-wireshark-1.4.9-to-1.4.10.diff.bz2) =
> c07c d875 4eda 13e7 5ff6 5fc6 4519 f7b6 935a 8dc4
> RIPEMD160(patch-wireshark-1.4.9-to-1.4.10.diff.bz2) =
> c9b1 d24f 1ae1 6f19 dec1 6da9 594d af40 116b c393
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.11 (Darwin)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
>
> iEYEARECAAYFAk6wTCQACgkQpw8IXSHylJq1zQCfaQxU15uufFQUS2U+dl4yOPuh
> 3McAoJ5BVG1/2wr5OlZQzmX8O5iQStky
> =uShV
> -----END PGP SIGNATURE-----
> ___________________________________________________________________________
> Sent via: Wireshark-dev mailing list <wireshark-dev@wireshark.org>
> Archives: http://www.wireshark.org/lists/wireshark-dev
> Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
> mailto:wireshark-dev-request@wireshark.org?subject=unsubscribe
>

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