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).
18 lines
696 B
C++
18 lines
696 B
C++
#pragma once
|
|
|
|
#include <vanetza/security/ecdsa256.hpp>
|
|
#include <vanetza/security/pqc/fndsa512.hpp>
|
|
#include <vanetza/security/v3/certificate.hpp>
|
|
#include <string>
|
|
|
|
vanetza::security::ecdsa256::KeyPair load_ecc_key_pair(const std::string& path);
|
|
vanetza::security::pqc::KeyPair load_pqc_key_pair(const std::string& base_path);
|
|
vanetza::security::pqc::PrivateKey load_pqc_private_key(const std::string& base_path);
|
|
|
|
void save_pqc_key_pair(
|
|
const std::string& base_path, const vanetza::security::pqc::KeyPair&);
|
|
|
|
vanetza::security::v3::Certificate load_v3_certificate(const std::string& path);
|
|
void save_v3_certificate(
|
|
const std::string& path, const vanetza::security::v3::Certificate&);
|