Files
MicrOBU/microbu-esp32c5/external/vanetza-idf/tools/pki/certificate_storage.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

28 lines
694 B
C++

#pragma once
#include "certificate.hpp"
#include "hashed_id8.hpp"
#include <boost/optional/optional.hpp>
#include <boost/range/any_range.hpp>
namespace vanetza
{
namespace pki
{
/// \brief Lazy, single-pass view over stored HashedId8s.
using HashedId8Range = boost::any_range<HashedId8, boost::single_pass_traversal_tag, HashedId8, std::ptrdiff_t>;
class CertificateStorage
{
public:
virtual ~CertificateStorage() = default;
virtual boost::optional<Certificate> fetch(const HashedId8&) const = 0;
virtual void store(const Certificate&) = 0;
virtual bool erase(const HashedId8&) = 0;
virtual HashedId8Range list() const = 0;
};
} // namespace pki
} // namespace vanetza