Parse Trust Tokens key commitments.
Trust Tokens key commitment responses are served during the issuance and redemption steps of the Trust Tokens (Privacy Pass) protocol. As part of implementing Trust Tokens, we need to fetch and parse these responses during the "issuance" and "redemption" protocol steps, triggered by requests' having been tagged with the corresponding fetch flags. For the preliminary version, these key commitment responses' contents are specified in the design doc: https://docs.google.com/document/d/1TNnya6B8pyomDK2F1R9CL3dY10OAmqWlnCxsWyOBDVQ/edit#bookmark=id.6wh9crbxdizi This CL adds parsing code; a concurrent change adds a flow for requesting these records from issuers' key commitment endpoints. New code: - KeyCommitmentResult describes the information we get from a key commitment response; - key_commitment_parsing.* implement logic and tests for parsing the commitments. We try to err on the side of being very strict, rejecting outright many messages that have any part malformed (for instance, if a record contains three keys and one is bad, the entire message gets thrown out). Bug: 1042962 Change-Id: I3b3d9b0b71bc74f80839b0f14309b990bcbe5a09 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2029292 Commit-Queue: David Van Cleve <davidvc@chromium.org> Reviewed-by:Charlie Harrison <csharrison@chromium.org> Cr-Commit-Position: refs/heads/master@{#748677}
Showing
This diff is collapsed.
Please register or sign in to comment