Ashin Walpola
d107534eb2
obu-firmware builds against the vanetza-idf C-ITS library, which until now came from the colleague's microbu-esp32c5 tree beside the repository and was not tracked here, so a clone of this repository could not build the firmware it ships. The library alone is now part of obu-firmware, as obu-firmware/external/vanetza-idf: their external/vanetza-idf at commit cf4b99f, unchanged (9775 files; see its PROVENANCE.md). CMake takes it from there by default; -DVANETZA_IDF_DIR still points the build elsewhere. The rest of the colleague's tree (their own VAM firmware, PKI tooling, station-link Python tools, the V2X2MAP bridge) stays out of this repository and gitignored; nothing is pushed to their repository. NOTES.md, docs/06, TODO.md and the pcap verifier's usage line point at the new location.
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
|