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.
44 lines
953 B
C++
44 lines
953 B
C++
#include <vanetza/security/v2/subject_info.hpp>
|
|
#include <vanetza/security/v2/length_coding.hpp>
|
|
|
|
namespace vanetza
|
|
{
|
|
namespace security
|
|
{
|
|
namespace v2
|
|
{
|
|
|
|
size_t get_size(const SubjectInfo& sub)
|
|
{
|
|
size_t size = sizeof(sub.subject_type);
|
|
size += sub.subject_name.size();
|
|
size += length_coding_size(sub.subject_name.size());
|
|
return size;
|
|
}
|
|
|
|
void serialize(OutputArchive& ar, const SubjectInfo& sub)
|
|
{
|
|
serialize(ar, sub.subject_type);
|
|
size_t size = sub.subject_name.size();
|
|
serialize_length(ar, size);
|
|
for (auto& byte : sub.subject_name) {
|
|
ar << byte;
|
|
}
|
|
}
|
|
|
|
size_t deserialize(InputArchive& ar, SubjectInfo& sub)
|
|
{
|
|
deserialize(ar, sub.subject_type);
|
|
const std::uintmax_t size = deserialize_length(ar);
|
|
for (uintmax_t c = 0; c < size; ++c) {
|
|
uint8_t tmp;
|
|
ar >> tmp;
|
|
sub.subject_name.push_back(tmp);
|
|
}
|
|
return get_size(sub);
|
|
}
|
|
|
|
} // ns v2
|
|
} // ns security
|
|
} // ns vanetza
|