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).
33 lines
780 B
C++
33 lines
780 B
C++
#pragma once
|
|
|
|
#include "keys.hpp"
|
|
#include <vanetza/common/byte_buffer.hpp>
|
|
#include <boost/optional/optional.hpp>
|
|
#include <filesystem>
|
|
#include <string>
|
|
|
|
namespace vanetza
|
|
{
|
|
namespace pki
|
|
{
|
|
|
|
boost::optional<PrivateKey> parse_pem_private_key(const std::string&);
|
|
boost::optional<PrivateKey> parse_pem_private_key(const ByteBuffer&);
|
|
|
|
/**
|
|
* Encode an EC private key as unencrypted PKCS#8 PEM.
|
|
* Round-trips through parse_pem_private_key.
|
|
*/
|
|
std::string make_pem(const PrivateKey&);
|
|
|
|
/**
|
|
* Encode `priv` as PEM and write it to `path`.
|
|
*
|
|
* \throws std::runtime_error if the file cannot be created
|
|
* \throws OpenSslException on write failure
|
|
*/
|
|
void write_pem_private_key(const PrivateKey& priv, const std::filesystem::path& path);
|
|
|
|
} // namespace pki
|
|
} // namespace vanetza
|