Wireshark-announce: [Wireshark-announce] Wireshark 1.2.1 is now available
Date Prev
·
Date Next
·
Thread Prev
·
Thread Next
From: Wireshark announcements <wireshark-announce@xxxxxxxxxxxxx>
Date: Mon, 20 Jul 2009 11:24:15 -0700
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
I'm proud to announce the release of Wireshark 1.2.1.
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. See the security
advisory for details and a workaround.
o The IPMI dissector could overrun a buffer.
Versions affected: 1.2.0
o The AFS dissector could crash.
Versions affected: 0.9.2 to 1.2.0
o The Infiniband dissector could crash on some platforms.
Versions affected: 1.0.6 to 1.2.0
o The Bluetooth L2CAP dissector could crash.
Versions affected: 1.2.0
o The RADIUS dissector could crash.
Versions affected: 1.2.0
o The MIOP dissector could crash.
Versions affected: 1.2.0
o The sFlow dissector could use excessive CPU and memory.
Versions affected: 1.2.0
The following bugs have been fixed:
o Wireshark could crash while reading a pcap-ng file.
o Wireshark could crash while reading a PacketLogger file.
o CFLOW decoding is wrong for IPv6 fields (Bug 3328)
o packet-dcm, corrupt DICOM export files (Bug 3493)
o GeoIP map should use random temporary file name (Bug 3530)
o Wireshark crashes when range_string is the data type (Bug
3536)
o Pcap-ng breaks VoIP call data (Bug 3539)
o ANSI MAP legInformation BER Error (Bug 3541)
o Starting Wireshark Portable 1.2.0 gives error message. (Bug
3547)
o On Windows, Wireshark could crash on startup. (Bug 3555)
o The title in the TCP sequence graphs is too short. (Bug 3556)
o USB Packets in pcap-ng Files Not Dissected Properly (Bug 3560)
o 802.11 decryption is broken (Bug 3590)
o SMB2 Error Response doesn't decode properly (Bug 3609)
o configure.in uses deprecated autoconf test for gnutls
detection (Bug 3627)
o Radius Malformed Packet error message (Bug 3635)
o Wireshark could crash when loading a profile. (Bug 3640)
o Analyze->Decode as... menu item becomes unavailable (Bug 3642)
o btsnoop: Incorrect error message for not supported datalink
type (Bug 3645)
o Decode error for network-id in BICC BCU-ID (Bug 3648)
o IEC 60870-5-104 dissector decodes nothing (Bug 3650)
o radius_register_avp_dissector() can stop RADIUS dissector from
working correctly (Bug 3651)
o ANSI ISUP Cause indicators with coding standard=ANSI fail to
dissect. (Bug 3654)
o Wrong field position in PacketCable Multimedia Extended
Classifier (Bug 3656)
o FF Protocol "FMS Initiate - Version OD Calling" field packet
data not unpacked properly (Bug 3694)
o hci_h4: Optimize column/field handling (Bug 3703)
o BSSLAP Protocol Not Decoded In BSSMAP-LE Messages (Bug 3711)
o Description of tshark -t dd missing from tshark.pod (Bug 3723)
o Problem in packet-per.c for ASN.1 PER Encoding (Bug 3733)
o [SNMP] Crash when dissecting packet (custom MIB) (Bug 3746)
New and Updated Features
There are no new or updated features in this release.
New Protocol Support
There are no new protocols in this release.
Updated Protocol Support
AFS, ANSI ISUP, ANSI MAP, ASN.1 PER, Bluetooth HCI H4, Bluetooth
L2CAP, BSS CFLOW, COPS, Diameter, DICOM, FF-HSE, ICMPv6,
IEC-60870-5-104, IEEE 802.11, Infiniband, IPMI, MIOP, RADIUS,
RSVP, sFlow, SNMP, SMB2, ZIOP
New Capture File Support
Btsnoop, DCT3, Packetlogger, pcap-ng.
Getting Wireshark
Wireshark source code and installation packages are available from
the download page on the main web site.
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 may appear offscreen on multi-monitor Windows systems.
(Bug 553)
Wireshark might make your system disassociate from a wireless
network on OS X. (Bug 1315)
Dumpcap might not quit if Wireshark or TShark crashes. (Bug 1419)
The BER dissector might infinitely loop. (Bug 1516)
Wireshark can't dynamically update the packet list. This means
that host name resolutions above a certain response time threshold
won't show up in the packet list. (Bug 1605)
Capture filters aren't applied when capturing from named pipes.
(Bug 1814)
Wireshark might freeze when reading from a pipe. (Bug 2082)
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.
Getting Help
Community support is available on the wireshark-users mailing
list. Subscription information and archives for all of Wireshark's
mailing lists can be found on the web site.
Commercial support, training, and development services are
available from CACE Technologies.
Frequently Asked Questions
A complete FAQ is available on the Wireshark web site.
Digests
wireshark-1.2.1.tar.bz2: 15129422 bytes
MD5(wireshark-1.2.1.tar.bz2)=957d1b11a6c9b305bcd106d4084ff71e
SHA1(wireshark-1.2.1.tar.bz2)=ff565edd4b8c7b8d131060145dd35873c0dd8fa9
RIPEMD160(wireshark-1.2.1.tar.bz2)=335814f79b56805b2dc5c130b2b91ed9b33d1591
wireshark-1.2.1.tar.gz: 19236508 bytes
MD5(wireshark-1.2.1.tar.gz)=56d760eeec0001b9a0b816ace3e99e44
SHA1(wireshark-1.2.1.tar.gz)=89b643edb8d5aa9271711118fadb7559027e594a
RIPEMD160(wireshark-1.2.1.tar.gz)=93bf4e5fe2720dc3318b43c43b21ed5070cd2630
wireshark-win32-1.2.1.exe: 18268341 bytes
MD5(wireshark-win32-1.2.1.exe)=266d95bc850cadebc2fa07ef3364c549
SHA1(wireshark-win32-1.2.1.exe)=be64cc1c57f433ffa5931c54f0946b2f504c4f74
RIPEMD160(wireshark-win32-1.2.1.exe)=6e8a56e0fddcfbd0991ded9ed8090eaded46eed2
wireshark-win64-1.2.1.exe: 14578262 bytes
MD5(wireshark-win64-1.2.1.exe)=f73bf17191f77b378993a6dcb0daccbc
SHA1(wireshark-win64-1.2.1.exe)=78ec2ce008cd79685b699f416c9cf554fdf68fe9
RIPEMD160(wireshark-win64-1.2.1.exe)=f2a8bb03ea7e9f92068131904abf5e660c0e3acc
wireshark-1.2.1.u3p: 21384889 bytes
MD5(wireshark-1.2.1.u3p)=17eb4980aefb8d50d8e634b6dedff2f9
SHA1(wireshark-1.2.1.u3p)=a98b4478b4c33a8c4dbfd08bbe6be454fdeff71d
RIPEMD160(wireshark-1.2.1.u3p)=50443d794672de83178aef118b67883b594c2c46
WiresharkPortable-1.2.1.paf.exe: 19088751 bytes
MD5(WiresharkPortable-1.2.1.paf.exe)=8fa3277e9848a087c26683a180450d7c
SHA1(WiresharkPortable-1.2.1.paf.exe)=451f5298c5d76667fe96698a62acc0db702e3936
RIPEMD160(WiresharkPortable-1.2.1.paf.exe)=7fc0f0e64e6c3902fb01b94a31e113ff92f63846
Wireshark 1.2.1 Intel.dmg: 36109430 bytes
MD5(Wireshark 1.2.1 Intel.dmg)=dae7e98730b9d1b437e368603dbc7ede
SHA1(Wireshark 1.2.1 Intel.dmg)=00f43c96d045ba2af36c3059d62821cc30c45811
RIPEMD160(Wireshark 1.2.1
Intel.dmg)=a3163736a0c5fc22be90239c8b4dfa20b25648b1
Wireshark 1.2.1 PPC.dmg: 38979007 bytes
MD5(Wireshark 1.2.1 PPC.dmg)=4436bafc315eba5b0cb5e59b698452d8
SHA1(Wireshark 1.2.1 PPC.dmg)=321c273b8f7b4af5afcb0627ec778412d12c489e
RIPEMD160(Wireshark 1.2.1 PPC.dmg)=18711bb3b6ae0de4018b4ea24775bbc596a1285e
patch-wireshark-1.2.0-to-1.2.1.diff.bz2: 296259 bytes
MD5(patch-wireshark-1.2.0-to-1.2.1.diff.bz2)=c9c384ff91ccced170981a2edfcc18ee
SHA1(patch-wireshark-1.2.0-to-1.2.1.diff.bz2)=bc012ae61ae385a8d86aef9daa3dfade25b738bd
RIPEMD160(patch-wireshark-1.2.0-to-1.2.1.diff.bz2)=a99b19e2c50a5d2310d3c706e1f4b3bba7200961
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (Darwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAkpktk8ACgkQpw8IXSHylJrqTwCfRQIpYCTJNHpU5sv2pwtFwrBT
a2IAoLWODSeWcxYoNgKGK4qxeQmfBXRK
=F0T3
-----END PGP SIGNATURE-----