Files
Ashin Walpola d107534eb2 Keep vanetza-idf in obu-firmware, so a plain clone builds the firmware
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.
2026-09-24 10:56:05 +02:00

30 lines
645 B
C++

#include <vanetza/security/v3/static_certificate_provider.hpp>
namespace vanetza
{
namespace security
{
namespace v3
{
StaticCertificateProvider::StaticCertificateProvider(const Certificate& authorization_ticket,
const PrivateKey& authorization_ticket_key) :
authorization_ticket(authorization_ticket),
authorization_ticket_key(authorization_ticket_key)
{
}
const PrivateKey& StaticCertificateProvider::own_private_key()
{
return authorization_ticket_key;
}
const Certificate& StaticCertificateProvider::own_certificate()
{
return authorization_ticket;
}
} // namespace v3
} // namespace security
} // namespace vanetza