Files
MicrOBU/microbu-esp32c5/external/vanetza-idf/vanetza/security/v2/trust_store.hpp
T
Ashin Walpola 0e9525162d Keep the colleague's microbu-esp32c5 tree in this repository
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).
2026-09-23 17:46:40 +02:00

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 */