r2511-v261030 Release Notes

New modules

• CSM — Crypto Service Manager daemon. Runs the key-slot and certificate operations of ara::crypto in an isolated daemon

Improvements to existing modules

• ara::com — IAM
  • Local IAM access control added
  • Remote IAM access control added
• ara::com — TLS
  • PSK key location changed: psk-identity.psk → tls-cipher-suites[].authenticationKey
• ara::crypto
  • Key-slot operations delegated to the CSM daemon
  • All 480 supported AlgIds verified exhaustively
• ara::exec
  • resource-group — cgroup v2 CPU and memory limits applied. The cpu-usage percentage is now relative to all cores of the machine instead of a single CPU
  • System-test verification added for startup-config.policy (fifo / round-robin) and priority
• ara::phm
  • Stricter manifest validation — names exceeding the wire limit, empty mode conditions, and more than one RecoveryNotification per health channel are handled as exceptions
• ara::log
  • fmt dependency removed — in-house para::log::Format formatter applied
• ara::diag
  • asio dependency removed from DiagnosticClient (DoIP test client) — replaced with POSIX sockets
• para-base — IPC
  • UDS/SHM transport hardened — MSG_NOSIGNAL, connect deadline, SHM region directory lock and layout validation
  • IPC decode length limit
• Build · packaging
  • S32G2 (aarch64) cross build · SM and IDSM included in the package
  • External dependencies trimmed — fmt · asio · iceoryx · libarchive removed

Bug fixes

• ara::com
  • 0x8000 bit applied to SOME/IP event Method IDs
  • Manifests with out-of-range event-id · method-id (> 32767) are now rejected at load
  • Fixed Unsubscribe() not being delivered to the provider for services offered with minor ≠ 0
  • Fixed the StartFindService handler not being invoked with an empty container when the provider calls StopOfferService()
• ara::exec
  • FG transitions starting from Undefined State (e.g. SetState Off) did not terminate surviving processes
  • Fixed core-affinity in the manifest being ignored
• ara::idsm
  • PRS IDS protocol alignment — Module Instance ID, protocol version, SEv context data, timestamps, etc.
  • Fixed event loss on an empty filter chain