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.
34 lines
704 B
C++
34 lines
704 B
C++
#ifndef CERTIFICATE_VALIDATOR_HPP
|
|
#define CERTIFICATE_VALIDATOR_HPP
|
|
|
|
//#include <vanetza/security/v2/certificate.hpp>
|
|
#include <vanetza/security/certificate_validity.hpp>
|
|
|
|
namespace vanetza
|
|
{
|
|
namespace security
|
|
{
|
|
namespace v2
|
|
{
|
|
|
|
struct Certificate;
|
|
|
|
class CertificateValidator
|
|
{
|
|
public:
|
|
/**
|
|
* Check validity of given certificate and consistency with parent certificates.
|
|
* \param certificate given certificate
|
|
* \return validity result
|
|
*/
|
|
virtual CertificateValidity check_certificate(const Certificate& certificate) = 0;
|
|
|
|
virtual ~CertificateValidator() = default;
|
|
};
|
|
|
|
} // namespace v2
|
|
} // namespace security
|
|
} // namespace vanetza
|
|
|
|
#endif // CERTIFICATE_VALIDATOR_HPP
|