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).
32 lines
786 B
C++
32 lines
786 B
C++
#pragma once
|
|
#include <vanetza/common/byte_buffer.hpp>
|
|
#include <array>
|
|
#include <cstdint>
|
|
|
|
namespace vanetza
|
|
{
|
|
namespace security
|
|
{
|
|
|
|
using HmacKey = std::array<uint8_t, 32>;
|
|
using KeyTag = std::array<uint8_t, 16>;
|
|
|
|
/**
|
|
* \brief generate HMAC key and create HMAC tag on data
|
|
* \param data data to be tagged
|
|
* \param hmacKey generated HMAC key
|
|
* \return tag of data generated with hmacKey
|
|
*/
|
|
KeyTag create_hmac_tag(const vanetza::ByteBuffer& data, const HmacKey& hmacKey);
|
|
|
|
#if defined VANETZA_WITH_OPENSSL
|
|
KeyTag create_hmac_tag_openssl(const vanetza::ByteBuffer& data, const HmacKey& hmacKey);
|
|
#endif
|
|
|
|
#if defined VANETZA_WITH_CRYPTOPP
|
|
KeyTag create_hmac_tag_cryptopp(const vanetza::ByteBuffer& data, const HmacKey& hmacKey);
|
|
#endif
|
|
|
|
} // namespace security
|
|
} // namespace vanetza
|