| commit | 54e0c9ae85de24404782b2df8bdbbb6442e2e71a | [log] [tgz] |
|---|---|---|
| author | Sui Chen <suichen@google.com> | Thu Sep 10 13:48:06 2020 -0700 |
| committer | Sui Chen <suichen@google.com> | Fri Oct 02 09:26:43 2020 -0700 |
| tree | 40514171ffaa2a2ef0148324496cd2e2748a1677 | |
| parent | 9723789d08fce61123c56a67208f5bd5fc7ae807 [diff] |
dbus-pcap: Parse headers of large messages
When encountering a large message that got truncated, instead of
raising a MalformedPacketError and completely ignoring the message,
parse as much as possible (in this case, its header) so that it can
still be used for certain purposes, such as to match method calls and
method returns.
Tested: compared against WireShark outputs (WireShark is able to handle
truncated messages) and manually inspecting parsed results.
One example message:
CookedMessage(header=CookedHeader(fixed=FixedHeader(endian=108, type=2,
flags=1, version=1, length=125272, cookie=3543),
fields=[Field(type=<MessageFieldType.REPLY_SERIAL: 5>, data=2),
Field(type=<MessageFieldType.DESTINATION: 6>, data=':1.1145'),
Field(type=<MessageFieldType.SIGNATURE: 8>, data='a{oa{sa{sv}}}'),
Field(type=<MessageFieldType.SENDER: 7>, data=':1.628')]), body=[])
Signed-off-by: Sui Chen <suichen@google.com>
Change-Id: Ie415735aef2b1c0bf6f27c509684964ccd87d1d9
The goal of this repository is to collect the two-minute hacks you write to automate interactions with OpenBMC systems.
It's highly likely the scripts don't meet your needs - they could be undocumented, dysfunctional or utterly broken. Please help us improve!
Then this repository aims to be the default destination for your otherwise un-homed scripts. As such we are setting the bar for submission pretty low, and we aim to make the process as easy as possible.
Please use gerrit for all patches to this repository:
Do note that you will need to be party to the OpenBMC CLA before your contributions can be accepted. See Gerrit Setup and CLA for more information.
So long as your patches look sane with a cursory glance you can expect them to be applied. We may push back in the event that similar tools already exist or there are egregious issues.
We don't ask for much, but you need to give us at least a Signed-off-by, use SPDX markers in your source files and put your work under an Apache 2.0 compatible license.
There's no standard way to install the scripts housed here, and adding parts of the repository to your PATH might be a bit of a dice-roll. We may also move or remove scripts from time to time as part of housekeeping. It's probably best to copy things out if you need stability.