Wireshark-bugs: [Wireshark-bugs] [Bug 6343] New: PostgreSQL Startup message not properly support
Date: Thu, 15 Sep 2011 02:00:54 -0700 (PDT)
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=6343

           Summary: PostgreSQL Startup message not properly supported by
                    the PostgreSQL dissector
           Product: Wireshark
           Version: SVN
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: Enhancement
          Priority: Low
         Component: TShark
        AssignedTo: [email protected]
        ReportedBy: [email protected]


Created an attachment (id=7018)
 --> (https://bugs.wireshark.org/bugzilla/attachment.cgi?id=7018)
Capture of a simple PostgreSQL session

Build Information:
wireshark 1.7.0 (SVN Rev 38992 from /trunk)

Copyright 1998-2011 Gerald Combs <[email protected]> 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 (32-bit) with GTK+ 2.24.4, with Cairo 1.10.2, with Pango 1.28.4, with
GLib 2.28.6, with libpcap 1.1.1, with libz 1.2.3.4, with POSIX capabilities
(Linux), with threads support, with SMI 0.4.8, with c-ares 1.7.3, with Lua 5.1,
with Python 2.7.1+, with GnuTLS 2.8.6, with Gcrypt 1.4.6, with MIT Kerberos,
with GeoIP, with PortAudio V19-devel (built Mar 18 2011 15:44:36), without
AirPcap.

Running on Linux 2.6.38-8-generic, with locale en_US.UTF-8, with libpcap
version
1.1.1, with libz 1.2.3.4, GnuTLS 2.8.6, Gcrypt 1.4.6.

Built using gcc 4.5.2.
--
The PostgreSQL dissector do not fully support the frontend StartupMessage (see
“StartupMessage” in
http://developer.postgresql.org/pgdocs/postgres/protocol-message-formats.html).
The couples parameter name/parameter value in this kind of message are reported
as a block of text (“name: value”) by the dissector whereas reporting them as
parameter name/parameter value would be more appropriate.

I’ve fixed it, so now the username and the database sent by the frontend can be
handled in, for instance, the CSV output of TShark.

I’ve also added a “val_count” field to contain the number of values (row
descriptions or row data) included in RowDescription/DataRow messages. This
information is useful when analyzing the CSV of TShark since in a CSV row, many
row descriptions or row data may be packed together.

With my changes to the PostgreSQL dissector, I’ve run successfully ~1200
iterations with teh fuzz-testing tool (tools/fuzz-test.sh) using the attached
capture.

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