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.
40 lines
1.0 KiB
C++
40 lines
1.0 KiB
C++
#include <vanetza/security/v2/static_certificate_provider.hpp>
|
|
|
|
namespace vanetza
|
|
{
|
|
namespace security
|
|
{
|
|
namespace v2
|
|
{
|
|
|
|
StaticCertificateProvider::StaticCertificateProvider(const Certificate& authorization_ticket,
|
|
const ecdsa256::PrivateKey& authorization_ticket_key) :
|
|
StaticCertificateProvider(authorization_ticket, authorization_ticket_key, std::list<Certificate> {})
|
|
{
|
|
}
|
|
|
|
StaticCertificateProvider::StaticCertificateProvider(const Certificate& authorization_ticket,
|
|
const ecdsa256::PrivateKey& authorization_ticket_key, const std::list<Certificate>& chain) :
|
|
authorization_ticket(authorization_ticket), authorization_ticket_key(authorization_ticket_key), chain(chain)
|
|
{
|
|
}
|
|
|
|
const ecdsa256::PrivateKey& StaticCertificateProvider::own_private_key()
|
|
{
|
|
return authorization_ticket_key;
|
|
}
|
|
|
|
std::list<Certificate> StaticCertificateProvider::own_chain()
|
|
{
|
|
return chain;
|
|
}
|
|
|
|
const Certificate& StaticCertificateProvider::own_certificate()
|
|
{
|
|
return authorization_ticket;
|
|
}
|
|
|
|
} // namespace v2
|
|
} // namespace security
|
|
} // namespace vanetza
|