Ashin Walpola
0e9525162d
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).
34 lines
747 B
C++
34 lines
747 B
C++
#ifndef NULL_CERTIFICATE_PROVIDER_HPP_3L9RJY2A
|
|
#define NULL_CERTIFICATE_PROVIDER_HPP_3L9RJY2A
|
|
|
|
#include <vanetza/security/v2/certificate_provider.hpp>
|
|
|
|
namespace vanetza
|
|
{
|
|
namespace security
|
|
{
|
|
namespace v2
|
|
{
|
|
|
|
class NullCertificateProvider : public CertificateProvider
|
|
{
|
|
public:
|
|
NullCertificateProvider();
|
|
|
|
const Certificate& own_certificate() override;
|
|
std::list<Certificate> own_chain() override;
|
|
const ecdsa256::PrivateKey& own_private_key() override;
|
|
|
|
/**
|
|
* Get static dummy certificate
|
|
* \return certificate filled with dummy values
|
|
*/
|
|
static const Certificate& null_certificate();
|
|
};
|
|
|
|
} // namespace v2
|
|
} // namespace security
|
|
} // namespace vanetza
|
|
|
|
#endif /* NULL_CERTIFICATE_PROVIDER_HPP_3L9RJY2A */
|