Wireshark 1.0.5

What's new in this version:

Bug Fixes
- The SMTP dissector could consume excessive amounts of CPU and memory.
- The WLCCP dissector could go into an infinte loop.

The following bugs have been fixed:
- Missing CRLF during HTTP POST in the "packet details" window
- Memory assertion in time_secs_to_str_buf() when compiled with GCC 4.2.3
- Diameter dissector fails RFC 4005 compliance
- LDP vendor private TLV type is not correctly shown
- Wireshark on MacOS does not run when there are spaces in its path
- OS X Intel package incorrectly claims to be Universal
- Compilation broke when compiling without zlib
- Memory leak: saved_repoid
- Memory leak: follow_info
- Memory leak: follow_info
- Memory leak: tacplus_data
- Memory leak: col_arrows
- Memory leak: col_arrows
- Incorrect address structure assigned for find_conversation() in WSP
- Memory leak with unistim in voip_calls
- Error parsing the BSSGP protocol
- Assertion thrown in fvalue_get_uinteger when decoding TIPC
- LUA script : Wireshark crashes after closing and opening again a window used by a listener.draw() function.

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
- ANSI MAP, BSSGP, CIP, Diameter, ENIP, GIOP, H.263, H.264, HTTP, MPEG PES, PostgreSQL, PPI, PTP, Rsync, RTP, SMTP, SNMP, STANAG 5066, TACACS, TIPC, WLCCP, WSP

New and Updated Capture File Support
- None

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.
- Wireshark might make your system disassociate from a wireless network on OS X.
- Dumpcap might not quit if Wireshark or TShark crashes.
- The BER dissector might infinitely loop.
- 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.
- Capture filters aren't applied when capturing from named pipes.
- Wireshark might freeze when reading from a pipe.
- Capturing from named pipes might be delayed on Windows.
- Filtering tshark captures with display filters (-R) no longer works.

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 and development services are available from CACE Technologies.

Frequently Asked Questions
- A complete FAQ is available on the Wireshark web site.