Skip to content
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

Addressing Carl's WGLC review #20

Merged
merged 3 commits into from
Aug 28, 2024
Merged

Addressing Carl's WGLC review #20

merged 3 commits into from
Aug 28, 2024

Conversation

henkbirkholz
Copy link
Member

fixes #13

@henkbirkholz henkbirkholz requested a review from letmaik as a code owner August 27, 2024 13:47
@@ -113,6 +113,8 @@ The obtained timestamp token is then added back as an unprotected header into th

In this context, timestamp tokens are similar to a countersignature {{-countersign}} made by the TSA.

The message imprint sent to the TSA ({{Section 2.4 of -TSA}}) MUST be the hash of the payload field of the COSE signed object.
Copy link
Collaborator

@thomas-fossati thomas-fossati Aug 27, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this is not the gist of Carl's comment. He wants us to factor out this paragraph instead, which is not CTT-specific:

In either case, to minimize dependencies, the hash algorithm SHOULD
be the same as the algorithm used for signing the COSE message.  This
may not be possible if the timestamp token has been obtained outside
the processing context in which the COSE object is assembled.

@thomas-fossati thomas-fossati merged commit cc8c030 into main Aug 28, 2024
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Carl's review
2 participants