Files
MicrOBU/microbu-esp32c5/external/vanetza-idf/vanetza/security/README.md
T
Ashin Walpola 0e9525162d Keep the colleague's microbu-esp32c5 tree in this repository
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).
2026-09-23 17:46:40 +02:00

1.8 KiB

Security

This is the security module of Vanetza. It implements the ETSI C-ITS security extension of the GeoNetworking protocol based on:

Implemented Features

Most features are implemented, including:

  • Security profiles including the CAM and DENM profile
  • Certificate requests for unknown certificates of other stations
  • Certificate validation for incoming messages

Missing Features

There are a few missing features, but the overall implementation is in a working state to send and receive secured messages. It has been verified to work correctly by interoperability tests with other implementations.

  • Revocation checks for certificate authorities
    Certificates of CAs can be revoked via CRLs. There will be a new standard for the corresponding protocol in May 2018. It will be a new version of ETSI TS 102 941.

  • v2: region checks for polygonal and identified regions
    There are TODO notes in the code of region.cpp within the is_within() functions. Implementing these checks is non-trivial.

  • v2: region consistency checks for regions other than circular and none region restrictions
    There are TODO notes in the code of region.cpp within the is_within() functions. Implementing these checks is non-trivial.

  • v3: region checks for identified regions

  • Certificate requests
    Currently there's no support to request authorization tickets from an authorization authority or to do an enrolment.