ashin-walpola/MicrOBU
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Keep vanetza-idf in obu-firmware, so a plain clone builds the firmware

Browse Source 
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.
This commit is contained in:
Ashin Walpola
2026-09-24 10:56:05 +02:00
parent 2f60623e18
commit d107534eb2
9781 changed files with 1560475 additions and 17 deletions
Download Patch File Download Diff File Expand all files Collapse all files
obu-firmware/external/vanetza-idf/docs/idf/evidence/security-host-07/analysis.md
Vendored
+20
View File
@@ -0,0 +1,20 @@
# security-host-07: AtsSecurity, CAM and DENM profiles (sending side)
Campaign: `ports/esp_idf/tests/etsi_security_facilities.cfg` (7 cases), same
SUT, pool and adapter as `security-host-06` (re-run of security-host-04 with the verifying SUT) (`adapter-build.json` is the same
link). The test application behind the GN upper tester port emits a CAM
carrier every second (`system.utPort.params := "cam_carrier_ms=1000"`) and a
DENM carrier on `UtDenmTrigger`; both are signed by the SUT's security entity
and verified by the framework against the pool (`enable_security_checks=1`).
| Case | Verdict | Observed |
| --- | --- | --- |
| TC_SEC_ITSS_SND_CAM_01..04_BV | pass | SHB/BTP-B CAM, psid 36, TS 103 097 clause 7.1.1 profile (signer digest, certificate once per second) |
| TC_SEC_ITSS_SND_DENM_01..03_BV | pass | GBC/BTP-B DENM, psid 37, clause 7.1.2 profile (generationLocation present) |
`AtsSecurity.framework-dathe-3.log` is the log of the `DENM Trigger` PTC of the
first DENM case; the two later PTC logs are identical in structure and were not
retained. No CA or DEN basic service is involved: the carriers are syntactically
valid Release 2 PDUs produced by the test application (`hil_sut.cpp`,
commands 7 and 8), which is what the testcases request through the upper
tester ("the IUT is requested to send a secured CAM/DENM").