Ashin Walpola
d107534eb2
obu-firmware builds against the vanetza-idf C-ITS library, which until now came from the colleague's microbu-esp32c5 tree beside the repository and was not tracked here, so a clone of this repository could not build the firmware it ships. The library alone is now part of obu-firmware, as obu-firmware/external/vanetza-idf: their external/vanetza-idf at commit cf4b99f, unchanged (9775 files; see its PROVENANCE.md). CMake takes it from there by default; -DVANETZA_IDF_DIR still points the build elsewhere. The rest of the colleague's tree (their own VAM firmware, PKI tooling, station-link Python tools, the V2X2MAP bridge) stays out of this repository and gitignored; nothing is pushed to their repository. NOTES.md, docs/06, TODO.md and the pcap verifier's usage line point at the new location.
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&);
|