[go: up one dir, main page]
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.

Sign up for GitHub

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

Jump to bottom

Add padding the payload to the aggregate explainer #1031

Merged
merged 1 commit into from Sep 26, 2023
Merged

Add padding the payload to the aggregate explainer #1031

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
Add padding the payload to the aggregate explainer 
See #352 and the spec change #1030.
  • Loading branch information
@alexmturner
alexmturner committed Sep 19, 2023
commit 0e31a94b1b95a03a878d347431897c9308034ba0
9 changes: 6 additions & 3 deletions AGGREGATE.md
View file
Open in desktop
Expand Up @@ -289,9 +289,12 @@ encoded. The map will have the following structure:
}, ...]
}
```
Optionally, the browser may encode multiple contributions in the same payload;
this is only possible if all other fields in the report/payload are identical
for the contributions.
The browser may encode multiple contributions in the same payload; this is only
possible if all other fields in the report/payload are identical for the
contributions. To avoid revealing the number of contributions in the payload
through its encrypted size, the browser should pad the list of payloads with
'null' (zero value) contributions up to the maximum. In the future, a more
direct padding scheme could be considered.

This encryption should use [AEAD](https://en.wikipedia.org/wiki/Authenticated_encryption)
to ensure that the information in `shared_info` is not tampered with, since the
Expand Down