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.
42 lines
972 B
C++
42 lines
972 B
C++
#ifndef DCC78C84_AD24_4E47_AEC4_C0ECB1127E03
|
|
#define DCC78C84_AD24_4E47_AEC4_C0ECB1127E03
|
|
|
|
#include <vanetza/security/hashed_id.hpp>
|
|
#include <vanetza/security/v2/certificate.hpp>
|
|
#include <list>
|
|
#include <map>
|
|
|
|
namespace vanetza
|
|
{
|
|
namespace security
|
|
{
|
|
namespace v2
|
|
{
|
|
|
|
class TrustStore
|
|
{
|
|
public:
|
|
/**
|
|
* Lookup certificates based on the passed HashedId8.
|
|
*
|
|
* \param id hash identifier of the certificate
|
|
* \return all stored certificates matching the passed identifier
|
|
*/
|
|
std::list<Certificate> lookup(HashedId8 id) const;
|
|
|
|
/**
|
|
* Insert a certificate into store, i.e. consider it as trustworthy.
|
|
* \param trusted_certificate a trustworthy certificate copied into TrustStore
|
|
*/
|
|
void insert(const Certificate& trusted_certificate);
|
|
|
|
private:
|
|
std::multimap<HashedId8, Certificate> m_certificates;
|
|
};
|
|
|
|
} // namespace v2
|
|
} // namespace security
|
|
} // namespace vanetza
|
|
|
|
#endif /* DCC78C84_AD24_4E47_AEC4_C0ECB1127E03 */
|