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).
44 lines
974 B
C++
44 lines
974 B
C++
#ifndef A137DCCA_FFB9_4D91_8441_D559E6F17C14
|
|
#define A137DCCA_FFB9_4D91_8441_D559E6F17C14
|
|
|
|
#include <vanetza/security/ecdsa256.hpp>
|
|
#include <vanetza/security/v2/certificate.hpp>
|
|
#include <list>
|
|
|
|
namespace vanetza
|
|
{
|
|
namespace security
|
|
{
|
|
namespace v2
|
|
{
|
|
|
|
class CertificateProvider
|
|
{
|
|
public:
|
|
/**
|
|
* Get own certificate to use for signing
|
|
* \return own certificate
|
|
*/
|
|
virtual const Certificate& own_certificate() = 0;
|
|
|
|
/**
|
|
* Get own certificate chain in root CA → AA → AT order, excluding the AT and root certificate
|
|
* \return own certificate chain
|
|
*/
|
|
virtual std::list<Certificate> own_chain() = 0;
|
|
|
|
/**
|
|
* Get private key associated with own certificate
|
|
* \return private key
|
|
*/
|
|
virtual const ecdsa256::PrivateKey& own_private_key() = 0;
|
|
|
|
virtual ~CertificateProvider() = default;
|
|
};
|
|
|
|
} // namespace v2
|
|
} // namespace security
|
|
} // namespace vanetza
|
|
|
|
#endif /* A137DCCA_FFB9_4D91_8441_D559E6F17C14 */
|