-
Notifications
You must be signed in to change notification settings - Fork 26
time feature request #1099
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
time feature request #1099
Conversation
:id: doc__time | ||
:status: valid | ||
:safety: ASIL_B | ||
:tags: change_management |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
feature_request
|
||
* External Time Synchronization | ||
* In-Vehicle Time Synchronization | ||
* Clocks, Accuracy, and Reading Current Time |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Could this item be defined a bit more clearly? E.g.
- Access to clocks including reading of current time
- Supporting calculus with points in time and time differences
- Determining accuracy of time read from each clock
- Secure Clocks: Used specifically in cryptographic contexts to validate digital certificates or ensure secure transaction timestamps; these require protection against tampering and robust synchronization. | ||
|
||
Programming languages typically abstract these clocks (e.g., ``std::chrono`` in C++, ``std::time`` in Rust). Therefore, the integration of S-CORE with existing language-specific abstractions is essential for consistency and ease of use. | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The integration should also enable calculus with points in time and time differences.
And it should be possible to serialize points in time and differences, so that they can be communicated with data via mw::com as well as be used during replay.
TODO: states of synchronized clocks, how to handle them? e.g. asking for current time when the clock is not synchronized. Error handling should be possible on per app use-case. | ||
TODO: should we expose the information on time difference since the last synchronization? dedicated api required. | ||
|
||
TODO: alignment with Crypto feature request on secure clocks |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Crypto needs:
A clock which provides authentic time in the sense it cannot be tampered with.
Rationale: prevent an adverse actor to reset time to an earlier wall clock/world clock in order enable a certificate which is already not anymore valid.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Could be called authentic time and signed in order to detect tampering.
No description provided.