Wireshark-bugs: [Wireshark-bugs] [Bug 974] New: RMCP dissector doesn't support "Secure RMCP" (AS
Date Index · Thread Index · Other Months · All Mailing Lists
Date Prev · Date Next · Thread Prev · Thread Next
From: bugzilla-daemon@xxxxxxxxxxxxx
Date: Wed, 21 Jun 2006 20:27:52 +0000 (GMT)
http://bugs.wireshark.org/bugzilla/show_bug.cgi?id=974

           Summary: RMCP dissector doesn't support "Secure RMCP" (ASF 2.0)
           Product: Wireshark
           Version: unspecified
          Platform: PC
        OS/Version: Windows XP
            Status: NEW
          Severity: Blocker
          Priority: Low
         Component: Wireshark
        AssignedTo: wireshark-bugs@xxxxxxxxxxxxx
        ReportedBy: swindell@xxxxxxxxxxxx


Ethereal already correctly parses ASF RMCP traffic, but doesn't recognize
"Secure RMCP" traffic (on UDP port 664), as defined in the ASF 2.0
specification.

See the attached capture of a valid Secure RMCP "Open Session" request and
response.

Here's a link to the ASF specification which defines the format of non-secure
RMCP (ASF 1.0) and Secure RMCP (ASF 2.0) packets:

http://www.dmtf.org/standards/documents/ASF/DSP0136.pdf

The difference between RMCP and Secure RMCP is that Secure RMCP traffic is
received on a different UDP port and the RMCP message is encapsulated in an RSP
header and trailer (defined in the ASF 2.0 specification reference above).


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