Wireshark · Wireshark-users: Re: [Wireshark-users] Wireshark 1.12.3 is now available

[Stephen <steve@xxxxxxxxxx>]

Hi Manish,

Both of these are current, just the latest version of two different
"trees". You can run either of them, however, I personally tend to go
for the "latest and greatest" branch - i.e. the 1.12. Hope that helps,

Stephen

On Thu, 08 Jan 2015, Manish . wrote:

> HI Friends,
> 
> I am confused with the two release of wireshark at a time (1.12.3 and 1.10.12)
> Can anyone of you please confirm which one is latest and recommended. Also request you to confirm which release is having upp, ranap megaco and iuup protocols.
> 
> Regards
> Manish Singla
> ________________________________________
> From: wireshark-users-bounces@xxxxxxxxxxxxx <wireshark-users-bounces@xxxxxxxxxxxxx> on behalf of Gerald Combs <gerald@xxxxxxxxxxxxx>
> Sent: Thursday, January 08, 2015 3:33 AM
> To: wireshark-announce@xxxxxxxxxxxxx; Community support list for Wireshark; Developer support list for Wireshark
> Subject: [Wireshark-users] Wireshark 1.12.3 is now available
> 
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> I'm proud to announce the release of Wireshark 1.12.3.
> 
>      __________________________________________________________________
> 
> 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.
>      * [1]wnpa-sec-2015-01
>        The WCCP dissector could crash. ([2]Bug 10720, ws-buglink:10806)
>      * [3]wnpa-sec-2015-02
>        The LPP dissector could crash. ([4]Bug 10773)
>      * [5]wnpa-sec-2015-03
>        The DEC DNA Routing Protocol dissector could crash. ([6]Bug 10724)
>      * [7]wnpa-sec-2015-04
>        The SMTP dissector could crash. ([8]Bug 10823)
> 
>    The following bugs have been fixed:
>      * WebSocket dissector: empty payload causes
>        DISSECTOR_ASSERT_NOT_REACHED. ([9]Bug 9332)
>      * Wireshark crashes if Lua heuristic dissector returns true. ([10]Bug
>        10233)
>      * Display MEP ID in decimal in OAM Y.1731 Synthetic Loss Message and
>        Reply PDU. ([11]Bug 10500)
>      * TCP Window Size incorrectly reported in Packet List. ([12]Bug
>        10514)
>      * Status bar "creeps" to the left a few pixels every time Wireshark
>        is opened. ([13]Bug 10518)
>      * E-LMI Message type. ([14]Bug 10531)
>      * SMTP decoder can dump binary data to terminal in TShark. ([15]Bug
>        10536)
>      * PTPoE dissector gets confused by packets that include an FCS.
>        ([16]Bug 10611)
>      * IPv6 Vendor Specific Mobility Option includes the next mobility
>        option type. ([17]Bug 10618)
>      * Save PCAP to PCAPng with commentary fails. ([18]Bug 10656)
>      * Display filter "frame contains bytes [2342]" causes a crash.
>        ([19]Bug 10690)
>      * Multipath TCP: checksum displayed when it's not there. ([20]Bug
>        10692)
>      * LTE APN-AMBR is decoded incorrectly. ([21]Bug 10699)
>      * DNS NAPTR RR Replacement Length is incorrect. ([22]Bug 10700)
>      * IPv6 Experimental mobility header data is interpreted as options.
>        ([23]Bug 10703)
>      * Dissector bug, protocol SPDY: tvbuff.c:610: failed assertion "tvb
>        && tvb->initialized". ([24]Bug 10704)
>      * BGP: Incorrect decoding AS numbers when mixed AS size. ([25]Bug
>        10742)
>      * BGP update community - incorrect decoding. ([26]Bug 10746)
>      * Setting a 6LoWPAN context generates a Wireshark crash. ([27]Bug
>        10747)
>      * FC is not dissected (protocol UNKNOWN). ([28]Bug 10751)
>      * Crash when displaying several times INFO column. ([29]Bug 10755)
>      * Decoding of longitude value in LCSAP (3GPP TS 29.171) is incorrect.
>        ([30]Bug 10767)
>      * Crash when enabling FCoIB manual settings without filling address
>        field. ([31]Bug 10796)
>      * RSVP RECORD_ROUTE IPv4 Subobject Flags field incorrect decoding.
>        ([32]Bug 10799)
>      * Wireshark Lua engine can't access protocol field type. ([33]Bug
>        10801)
>      * Field Analysis of OpenFlow v1.4 OFPT_SET_ASYNC. ([34]Bug 10808)
>      * Lua: getting fieldinfo.value for FT_NONE causes assert. ([35]Bug
>        10815)
> 
>   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
> 
>    6LoWPAN, ADwin, AllJoyn, Art-Net, Asterix, BGP, Bitcoin, Bluetooth
>    OBEX, Bluetooth SDP, CFM, CIP, DCERPC PN-IO, DCERPC SPOOLSS, DEC DNA,
>    DECT, DHCPv6, DNS, DTN, E-LMI, ENIP, Ethernet, Extreme, FCoIB, Fibre
>    Channel, GED125, GTP, H.248, H.264, HiSLIP, IDRP, IEEE 802.11, IEEE
>    P1722.1, Infiniband, IrDA, iSCSI, ISUP, LBMR, LCSAP, LPP, MAC LTE,
>    MAUSB, MBIM, MIM, MIP, MIPv6, MP2T, MPEG-1, NAS EPS, NAT-PMP, NCP, NXP
>    PN532, OpcUa, OpenFlow, PTP, RDM, RPKI-RTR, RSVP, RTnet, RTSP, SCTP,
>    SMPP, SMTP, SPDY, Spice, TCP, WCCP, Wi-Fi P2P, and WiMAX
> 
>   New and Updated Capture File Support
> 
>    and K12
>      __________________________________________________________________
> 
> Getting Wireshark
> 
>    Wireshark source code and installation packages are available from
>    [36]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 [37]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. ([38]Bug 1419)
> 
>    The BER dissector might infinitely loop. ([39]Bug 1516)
> 
>    Capture filters aren't applied when capturing from named pipes.
>    ([40]Bug 1814)
> 
>    Filtering tshark captures with read filters (-R) no longer works.
>    ([41]Bug 2234)
> 
>    The 64-bit Windows installer does not support Kerberos decryption.
>    ([42]Win64 development page)
> 
>    Resolving ([43]Bug 9044) reopens ([44]Bug 3528) so that Wireshark no
>    longer automatically decodes gzip data when following a TCP stream.
> 
>    Application crash when changing real-time option. ([45]Bug 4035)
> 
>    Hex pane display issue after startup. ([46]Bug 4056)
> 
>    Packet list rows are oversized. ([47]Bug 4357)
> 
>    Wireshark and TShark will display incorrect delta times in some cases.
>    ([48]Bug 4985)
>      __________________________________________________________________
> 
> Getting Help
> 
>    Community support is available on [49]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 [50]the web site.
> 
>    Official Wireshark training and certification are available from
>    [51]Wireshark University.
>      __________________________________________________________________
> 
> Frequently Asked Questions
> 
>    A complete FAQ is available on the [52]Wireshark web site.
>      __________________________________________________________________
> 
>    Last updated 2015-01-07 12:11:42 PST
> 
> References
> 
>    1. https://www.wireshark.org/security/wnpa-sec-2015-01.html
>    2. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=10720
>    3. https://www.wireshark.org/security/wnpa-sec-2015-02.html
>    4. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=10773
>    5. https://www.wireshark.org/security/wnpa-sec-2015-03.html
>    6. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=10724
>    7. https://www.wireshark.org/security/wnpa-sec-2015-04.html
>    8. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=10823
>    9. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=9332
>   10. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=10233
>   11. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=10500
>   12. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=10514
>   13. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=10518
>   14. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=10531
>   15. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=10536
>   16. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=10611
>   17. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=10618
>   18. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=10656
>   19. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=10690
>   20. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=10692
>   21. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=10699
>   22. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=10700
>   23. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=10703
>   24. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=10704
>   25. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=10742
>   26. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=10746
>   27. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=10747
>   28. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=10751
>   29. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=10755
>   30. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=10767
>   31. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=10796
>   32. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=10799
>   33. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=10801
>   34. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=10808
>   35. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=10815
>   36. http://www.wireshark.org/download.html
>   37. http://www.wireshark.org/download.html#thirdparty
>   38. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=1419
>   39. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=1516
>   40. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=1814
>   41. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=2234
>   42. http://wiki.wireshark.org/Development/Win64
>   43. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=9044
>   44. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=3528
>   45. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=4035
>   46. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=4056
>   47. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=4357
>   48. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=4985
>   49. http://ask.wireshark.org/
>   50. http://www.wireshark.org/lists/
>   51. http://www.wiresharktraining.com/
>   52. http://www.wireshark.org/faq.html
> 
> 
> Digests
> 
> wireshark-1.12.3.tar.bz2: 29211228 bytes
> MD5(wireshark-1.12.3.tar.bz2)=e6318b8451d4e56d39bd911da296ef19
> SHA1(wireshark-1.12.3.tar.bz2)=44ad77b6e80f41ba34ac0eaf477b81cb1345ceed
> RIPEMD160(wireshark-1.12.3.tar.bz2)=ca1697fb5819874a1c37c7863faa4ec57b2e3216
> 
> Wireshark-win64-1.12.3.exe: 29826488 bytes
> MD5(Wireshark-win64-1.12.3.exe)=a4bc638c0fafb850904908ca48c2295d
> SHA1(Wireshark-win64-1.12.3.exe)=c29fded55b678c34d9f504f994dcfa7a8dcb6e00
> RIPEMD160(Wireshark-win64-1.12.3.exe)=f0eeb1795e94751d726e02aa8390e6ed059ed772
> 
> Wireshark-win32-1.12.3.exe: 23579536 bytes
> MD5(Wireshark-win32-1.12.3.exe)=4067776d7173321f890e1bc1b10c8965
> SHA1(Wireshark-win32-1.12.3.exe)=e3748a0c7cddfcc5e27aed2f9e7bb3b28bf2e9fd
> RIPEMD160(Wireshark-win32-1.12.3.exe)=2ee5fa3e225cde38c778a0821ab0a64bfc436969
> 
> WiresharkPortable-1.12.3.paf.exe: 29876416 bytes
> MD5(WiresharkPortable-1.12.3.paf.exe)=5ed751bf868addc2fd8c787ae798aa1c
> SHA1(WiresharkPortable-1.12.3.paf.exe)=21a2882c69a30e080c057b81d3ef55abd332f50e
> RIPEMD160(WiresharkPortable-1.12.3.paf.exe)=9e6e774d4c303609094f1040ba92fd4c645a0fe7
> 
> Wireshark 1.12.3 Intel 32.dmg: 21825303 bytes
> MD5(Wireshark 1.12.3 Intel 32.dmg)=486a6484e16fb396ca6fea3d125d40c8
> SHA1(Wireshark 1.12.3 Intel
> 32.dmg)=7a9d9f371e139dc465a23948f3341e3d1ba6e620
> RIPEMD160(Wireshark 1.12.3 Intel
> 32.dmg)=02bf554b9dbf0f865dbd2a2e5ced3991f5ef4734
> 
> Wireshark 1.12.3 Intel 64.dmg: 26392514 bytes
> MD5(Wireshark 1.12.3 Intel 64.dmg)=7ddb0e9e6923fc01ee4abfd01bed52af
> SHA1(Wireshark 1.12.3 Intel
> 64.dmg)=4ae91fcd3a7b0c0b7fd88170fa35e558442d5682
> RIPEMD160(Wireshark 1.12.3 Intel
> 64.dmg)=edb4a5ea70e4f08cd743a5d6ff361f94c9109a5c
> 
> patch-wireshark-1.12.2-to-1.12.3.bz2: 354678 bytes
> MD5(patch-wireshark-1.12.2-to-1.12.3.bz2)=3607bfc80aa479bee926976cd1037f91
> SHA1(patch-wireshark-1.12.2-to-1.12.3.bz2)=b08617868ce130cb234f2d0124e2fcb1714981d0
> RIPEMD160(patch-wireshark-1.12.2-to-1.12.3.bz2)=fbbf1a0fc45a9697450698ccdd157bb189c8c570
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1
> 
> iEYEARECAAYFAlStrTUACgkQpw8IXSHylJo3owCgr0Qb1uHmLXnYEUeEcxRzKVda
> 0coAoNj4v6+VsNwoHNH9d3GUUpbxQTj6
> =TKuv
> -----END PGP SIGNATURE-----
> ___________________________________________________________________________
> 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
> "DISCLAIMER: This message is proprietary to Aricent and is intended solely for the use of the individual to whom it is addressed. It may contain privileged or confidential information and should not be circulated or used for any purpose other than for what it is intended. If you have received this message in error, please notify the originator immediately. If you are not the intended recipient, you are notified that you are strictly prohibited from using, copying, altering, or disclosing the contents of this message. Aricent accepts no responsibility for loss or damage arising from the use of the information transmitted by this email including damage from virus."
> ___________________________________________________________________________
> 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