Files
MicrOBU/obu-firmware/external/vanetza-idf/vanetza/security/v2/tests/signer_info.cpp
T
Ashin Walpola d107534eb2 Keep vanetza-idf in obu-firmware, so a plain clone builds the firmware
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.
2026-09-24 10:56:05 +02:00

36 lines
1.0 KiB
C++

#include <gtest/gtest.h>
#include <vanetza/common/byte_sequence.hpp>
#include <vanetza/security/v2/certificate.hpp>
#include <vanetza/security/v2/signer_info.hpp>
#include <vanetza/security/v2/tests/check_signature.hpp>
#include <vanetza/security/v2/tests/check_signer_info.hpp>
#include <vanetza/security/tests/serialization.hpp>
using vanetza::random_byte_sequence;
using vanetza::security::create_random_ecdsa_signature;
using vanetza::security::HashedId8;
using namespace vanetza::security::v2;
TEST(SignerInfo, Serialization)
{
std::list<Certificate> certificates;
Certificate a;
a.signature = create_random_ecdsa_signature(28);
Certificate b;
b.signature = create_random_ecdsa_signature(29);
certificates.push_back(a);
certificates.push_back(b);
SignerInfo info { certificates };
check(info, serialize_roundtrip(info));
}
TEST(SignerInfo, WebValidator_Size)
{
SignerInfo info;
HashedId8 id {{ 0xA8, 0xED, 0x6D, 0xF6, 0x5B, 0x0E, 0x6D, 0x6A }};
info = id;
EXPECT_EQ(9, get_size(info));
}