Ashin Walpola
0e9525162d
obu-firmware builds against vanetza-idf from microbu-esp32c5/external, but that tree was gitignored, so a clone of this repository could not build the firmware it ships. It is now committed here as ordinary files in its own folder, microbu-esp32c5/: the colleague's commit cf4b99f plus the V2X2MAP bridge's signature verification (--trust) used on the bench. Nothing is fetched from or pushed to the colleague's repository; this repository and its remotes carry everything. The folder's own .gitignore keeps build output, downloaded components and private key material out, as it did there; the committed file set is identical to that repository's tracked files. The ESP32-C5 is still flashed from obu-firmware/, which only takes vanetza-idf from microbu-esp32c5/, so the two stay separate folders. FLASHING.md says how to take a newer version of the colleague's tree (copy it over the folder, rebuild, test, commit).
31 lines
794 B
C++
31 lines
794 B
C++
#ifndef VANETZA_ROUTER_FUZZING_CONTEXT_HPP
|
|
#define VANETZA_ROUTER_FUZZING_CONTEXT_HPP
|
|
|
|
#include <vanetza/common/manual_runtime.hpp>
|
|
#include <vanetza/dcc/interface.hpp>
|
|
#include <vanetza/geonet/router.hpp>
|
|
#include <vanetza/geonet/transport_interface.hpp>
|
|
#include <vanetza/geonet/tests/security_context.hpp>
|
|
|
|
namespace vanetza
|
|
{
|
|
|
|
class RouterFuzzingContext {
|
|
public:
|
|
RouterFuzzingContext();
|
|
void initialize();
|
|
void indicate(ByteBuffer&& buffer);
|
|
|
|
private:
|
|
ManualRuntime runtime;
|
|
SecurityContext security;
|
|
geonet::ManagementInformationBase mib;
|
|
std::unique_ptr<geonet::Router> router;
|
|
std::unique_ptr<dcc::RequestInterface> req_ifc;
|
|
std::unique_ptr<geonet::TransportInterface> ind_ifc;
|
|
};
|
|
|
|
} // namespace vanetza
|
|
|
|
#endif //VANETZA_ROUTER_FUZZING_CONTEXT_HPP
|