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).
15 lines
536 B
C++
15 lines
536 B
C++
#include "certificate_validation_v3.hpp"
|
|
|
|
std::unique_ptr<CertificateValidationV3> create_certificate_validation_v3(
|
|
const boost::program_options::variables_map&, const vanetza::Runtime& runtime,
|
|
vanetza::PositionProvider& positioning,
|
|
const vanetza::security::v3::LocationChecker& location_checker,
|
|
vanetza::security::Backend&)
|
|
{
|
|
return create_default_certificate_validation_v3(runtime, positioning, location_checker);
|
|
}
|
|
|
|
void add_certificate_validation_v3_options(boost::program_options::options_description&)
|
|
{
|
|
}
|