Huge thanks to our Platinum Members Endace and LiveAction,
and our Silver Member Veeam, for supporting the Wireshark Foundation and project.

Wireshark-bugs: [Wireshark-bugs] [Bug 4472] New: Incorrect parsing POP3 response to CAPA packet

Date: Tue, 9 Feb 2010 00:47:32 -0800 (PST)
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=4472

           Summary: Incorrect parsing POP3 response to CAPA packet
           Product: Wireshark
           Version: 1.3.x (Experimental)
          Platform: x86
        OS/Version: Windows XP
            Status: NEW
          Severity: Minor
          Priority: Low
         Component: Wireshark
        AssignedTo: wireshark-bugs@xxxxxxxxxxxxx
        ReportedBy: benderspb@xxxxx


Build Information:
wireshark 1.3.0 (SVN Rev 29916 from /trunk)

Copyright 1998-2009 Gerald Combs <gerald@xxxxxxxxxxxxx> and contributors.
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

Compiled with GTK+ 2.16.5, with GLib 2.20.4, with WinPcap (version unknown),
with libz 1.2.3, without POSIX capabilities, with libpcre 7.0, with SMI 0.4.8,
with c-ares 1.6.0, with Lua 5.1, without Python, with GnuTLS 2.8.1, with Gcrypt
1.4.4, with MIT Kerberos, with GeoIP, with PortAudio V19-devel (built Sep 14
2009), with AirPcap.

Running on Windows XP Service Pack 3, build 2600, with WinPcap version 4.1.1
(packet.dll version 4.1.0.1753), based on libpcap version 1.0 branch 1_0_rel0b
(20091008), GnuTLS 2.8.1, Gcrypt 1.4.4, without AirPcap.

Built using Microsoft Visual C++ 9.0 build 30729

--
Incorrect parsing POP3 packet (#4 in attachment) -- response to CAPA command.



RFC 2449:

An -ERR response indicates the capability command is not implemented and the
client will have to probe for capabilities as before. 
An +OK response is followed by a list of capabilities, one per line. Each
capability name MAY be followed by a single space and a space-separated list of
parameters. Each capability line is limited to 512 octets (including the CRLF).
The capability list is terminated by a line containing a termination octet
(".") and a CRLF pair. 

Possible Responses: +OK -ERR 
Examples:
C: CAPA 
S: +OK Capability list follows 
S: TOP 
S: USER 
S: SASL CRAM-MD5 KERBEROS_V4 
S: RESP-CODES 
S: LOGIN-DELAY 900 
S: PIPELINING 
S: EXPIRE 60 
S: UIDL 
S: IMPLEMENTATION Shlemazle-Plotz-v302 
S: .

-- 
Configure bugmail: https://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.