Files
MicrOBU/microbu-esp32c5/external/vanetza-idf/vanetza/security/v2/verification.hpp
T
Ashin Walpola 0e9525162d Keep the colleague's microbu-esp32c5 tree in this repository
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).
2026-09-23 17:46:40 +02:00

22 lines
660 B
C++

#pragma once
#include <vanetza/common/clock.hpp>
#include <vanetza/common/position_fix.hpp>
#include <vanetza/security/v2/certificate.hpp>
#include <vanetza/security/v2/secured_message.hpp>
namespace vanetza
{
namespace security
{
namespace v2
{
bool check_generation_time(const SecuredMessage& message, Clock::time_point now);
bool check_generation_location(const SecuredMessage& message, const Certificate& cert);
bool check_certificate_time(const Certificate& certificate, Clock::time_point now);
bool check_certificate_region(const Certificate& certificate, const PositionFix& position);
} // namespace v2
} // namespace security
} // namespace vanetza