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).
30 lines
698 B
C++
30 lines
698 B
C++
#pragma once
|
|
|
|
#include "vanetza/common/byte_buffer.hpp"
|
|
#include <array>
|
|
#include <cstdint>
|
|
#include <string>
|
|
|
|
namespace vanetza
|
|
{
|
|
|
|
namespace pki
|
|
{
|
|
|
|
std::string hexstring(const std::uint8_t* buf, std::size_t len);
|
|
std::string hexstring(const std::string& input);
|
|
std::string hexstring(const ByteBuffer& buffer);
|
|
|
|
template<size_t N> std::string hexstring(const std::array<std::uint8_t, N>& array)
|
|
{
|
|
return hexstring(array.data(), array.size());
|
|
}
|
|
|
|
// true iff input is a non-empty, even-length run of hex digits
|
|
bool is_valid_hexstring(const std::string& input);
|
|
|
|
// decode hex digits to raw bytes
|
|
std::string parse_hexstring(const std::string& input);
|
|
|
|
} // namespace pki
|
|
} // namespace vanetza
|