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).
This commit is contained in:
+66
@@ -0,0 +1,66 @@
|
||||
#ifndef BC8469A6_CC39_4826_A95E_DE639D68863B
|
||||
#define BC8469A6_CC39_4826_A95E_DE639D68863B
|
||||
|
||||
#include <boost/optional/optional.hpp>
|
||||
|
||||
namespace vanetza
|
||||
{
|
||||
namespace security
|
||||
{
|
||||
|
||||
enum class CertificateInvalidReason
|
||||
{
|
||||
Broken_Time_Period,
|
||||
Off_Time_Period,
|
||||
Unknown_Signer,
|
||||
Missing_Signature,
|
||||
Missing_Public_Key,
|
||||
Invalid_Signer,
|
||||
Invalid_Name,
|
||||
Excessive_Chain_Length,
|
||||
Off_Region,
|
||||
Inconsistent_With_Signer,
|
||||
Insufficient_ITS_AID,
|
||||
Missing_Subject_Assurance,
|
||||
};
|
||||
|
||||
class CertificateValidity
|
||||
{
|
||||
public:
|
||||
CertificateValidity() = default;
|
||||
|
||||
/**
|
||||
* Create CertificateValidity signalling an invalid certificate
|
||||
* \param reason Reason for invalidity
|
||||
*/
|
||||
CertificateValidity(CertificateInvalidReason reason) : m_reason(reason) {}
|
||||
|
||||
/**
|
||||
* \brief Create CertificateValidity signalling a valid certificate
|
||||
* This method is equivalent to default construction but should be more expressive.
|
||||
* \return validity
|
||||
*/
|
||||
static CertificateValidity valid() { return CertificateValidity(); }
|
||||
|
||||
/**
|
||||
* Check if status corresponds to a valid certificate
|
||||
* \return true if certificate is valid
|
||||
*/
|
||||
operator bool() const { return !m_reason; }
|
||||
|
||||
/**
|
||||
* \brief Get reason for certificate invalidity
|
||||
* This call is only safe if reason is available, i.e. check validity before!
|
||||
*
|
||||
* \return reason
|
||||
*/
|
||||
CertificateInvalidReason reason() const { return *m_reason; }
|
||||
|
||||
private:
|
||||
boost::optional<CertificateInvalidReason> m_reason;
|
||||
};
|
||||
|
||||
} // namespace security
|
||||
} // namespace vanetza
|
||||
|
||||
#endif /* BC8469A6_CC39_4826_A95E_DE639D68863B */
|
||||
Reference in New Issue
Block a user