Problematic use of multiple INFO_SRS within an RTPS
Source: Real-Time Innovations ( Gerardo Pardo-Castellote)
The RTPS spec allows a single RTPS message to contain multiple INFO_SRC submessages, effectively changing the Participant GUID of the sending Participant.
This seems problematic for DDS Security since the cryptograophic material is tied to that Participant GUID (e.g. the RTPS protection).
Also INFO_SRC does not work well with the new RTPS_HEADER_EXTENSION.
How commonly is this capability used? It is worth finding a way to make DDS-Security work with it or would it be better to disallow it.
Should it be disallowed just for DDS-Security or for DDS in general?
Reported: DDS-SECURITY 1.1b1 — Wed, 27 Sep 2023 13:24 GMT
Updated: Wed, 27 Sep 2023 16:47 GMT