qpid-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Chuck Rolke <cro...@redhat.com>
Subject Malframed AMQP packets are accepted
Date Fri, 23 Jun 2017 17:54:21 GMT
AMQP 1.0 spec states a specific order for message format 0 (MESSAGE-FORMAT). The frames in
the jira follow the spec correctly except they have simple str8-utf8 strings inserted between
the major sections. I just raised issue https://issues.apache.org/jira/browse/PROTON-1509
to describe the situation in detail.

* Wireshark correctly calls out the strings as they are encountered in the message byte stream
but it does not throw an expert warning that a string is not appropriate at that point in
the frame.

* Proton-C ignores the strings and finds later sections.

* Dispatch ignores the strings and finds later sections.

* AMQP.Net Lite ignores the strings and finds later sections. AMQP.Net Lite is a non-qpid
implementation.

I have not tried proton-j.

Across the board I'd like to see parsers call this some kind of framing error. Had wireshark
done so then Dispatch would not have had the framing issue for so long.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
For additional commands, e-mail: users-help@qpid.apache.org


Mime
View raw message