-
Key: DDSSEC12-108
-
Status: closed
-
Source: Real-Time Innovations ( Dr. Gerardo Pardo-Castellote, Ph.D.)
-
Summary:
Topic uses the DDS::Time_t which rolls over at 2038.
We should update to the newer definition to be adopted in DDS 1.6We may need to use a different type name to allow both to co-exist
Curent definition is this:extensibility(APPENDABLE) // After DDSSEC12-29 struct BuiltinLoggingType { octet facility; // Set to 0x0A (10). Indicates sec/auth msgs LoggingLevel severity; Time_t timestamp; // Since epoch 1970-01-01 00:00:00 +0000 (UTC) string hostname; // IP host name of originator string hostip; // IP address of originator string appname; // Identify the device or application string procid; // Process name/ID for syslog system string msgid; // Identify the type of message string message; // Free-form message // Note that certain string keys (SD-IDs) are reserved by IANA map<string, NameValuePairSeq> structured_data; };
-
Reported: DDS-SECURITY 1.1b1 — Tue, 20 Jun 2023 22:49 GMT
-
Disposition: Resolved — DDS-SECURITY 1.2
-
Disposition Summary:
Modify BuiltinLoggingType to use 64 bits to hold the timestamp seconds
Introduce a new Log topic that uses a 64-bit integer for the seconds.
Since this is defined as an "application-level" topic discovery and type matching will take care of interoperability with earlier versions of the specification.Old topic name is deprecated but an implementation can support it for backwards compatibility.
-
Updated: Mon, 17 Jun 2024 13:36 GMT
DDSSEC12 — secure log topic has a year 2038 issue
- Key: DDSSEC12-108
- OMG Task Force: DDS Security 1.2 RTF