Module trace

Module trace 

Source
Expand description

This module define the execution Traces.

Each Traces consist of several Steps, of which each has either an OutputAction or InputAction. This is a declarative way of modeling communication between Agents. The TraceContext holds data, also known as Knowledge, which is created by Agents during the concrete execution of the Trace. It also holds the Agents with the references to concrete PUT.

§Serializability of Traces

Each trace is serializable to JSON or even binary data. This helps at reproducing discovered security vulnerabilities during fuzzing. If a trace triggers a security vulnerability we can store it on disk and replay it when investigating the case. As traces depend on concrete implementations as discussed in the next section we need to link serialized data like strings or numerical IDs to functions implemented in Rust.

Structs§

ConfigTrace
ExecutionResult
Store the result of a trace execution for displaying or serializing
InputAction
Provide inputs to the Agent.
Knowledge
Knowledge describes an atomic piece of knowledge inferred by the crate::protocol::Extractable::extract_knowledge function Knowledge is made of the data, the source of the output, the TLS message type and the internal type.
KnowledgeStore
MetadataTrace
OutputAction
Advance the Agent’s state and process the produced output.
Precomputation
Query
RawKnowledge
RawKnowledge stores
Spawner
Step
StepExecution
StepNumber
Identify a step and a (prior) trace
StepNumberDesc
Trace
TraceContext
The TraceContext represents the state of an execution.
TraceExecution
Store the result of a trace execution to be printed in the cli or serialized for automated analysis

Enums§

Action
There are two action types OutputAction and InputAction.
ActionType 🔒
Source
Source stores the origin of a knowledge, whether the agent name or the label of the precomputation that produced it
StepNumberChange

Functions§

filter_knowledge 🔒
Should a specific knowledge be kept