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

32 lines
633 B
C++

#include <vanetza/security/v3/revocation_lookup.hpp>
namespace vanetza
{
namespace security
{
namespace v3
{
void RevocationMemoryLookup::revoke(const HashedId8& issuer, const HashedId8& cert)
{
m_revoked[issuer].insert(cert);
}
void RevocationMemoryLookup::clear(const HashedId8& issuer)
{
m_revoked.erase(issuer);
}
bool RevocationMemoryLookup::is_revoked(const HashedId8& issuer, const HashedId8& cert) const
{
auto it = m_revoked.find(issuer);
if (it == m_revoked.end()) {
return false;
}
return it->second.count(cert) != 0;
}
} // namespace v3
} // namespace security
} // namespace vanetza