-
Notifications
You must be signed in to change notification settings - Fork 4
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
more security considerations #24
Conversation
c85dcf7
to
6ad3420
Compare
Fix #16 Signed-off-by: Thomas Fossati <[email protected]>
6ad3420
to
59ef3da
Compare
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.
What about "caching" a TST before TTC or CTT? The TST basically tells at minimum "statement not younger than time in TST". By retrieving a TST and then using it later, you can shift that point "more into the past". That is probably is a threat, too?
Signed-off-by: Thomas Fossati <[email protected]>
In CTT that can't happen unless you can predict the COSE signature, i.e., the content of the datum.
Sorry, I don't understand this. You are making a similar point in #25 which I am also failing to grok. To me, a timestamp asserts the existence of a datum at least at the point in time when the timestamp for that datum is created. I cannot fathom an attack in which pushing the existence of the datum back in time is an attack on the intended use of the datum. |
Signed-off-by: Thomas Fossati <[email protected]>
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.
ltgm
Fix #16