-
Notifications
You must be signed in to change notification settings - Fork 175
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
Consider adding padding to payload #352
Labels
possible-future-enhancement
Feature request with no current decision on adoption
Comments
alexmturner
added a commit
that referenced
this issue
Mar 14, 2022
This partially addresses #352 by ensuring that no information about each contribution is revealed through the length of the value's encoding.
csharrison
added
the
possible-future-enhancement
Feature request with no current decision on adoption
label
Jun 26, 2023
Note the latest discussion of this is happening here: patcg-individual-drafts/private-aggregation-api#56 |
alexmturner
added a commit
that referenced
this issue
Sep 19, 2023
Resolves #352. See also related spec change for the Private Aggregation API: patcg-individual-drafts/private-aggregation-api#98
alexmturner
added a commit
that referenced
this issue
Sep 26, 2023
alexmturner
added a commit
that referenced
this issue
Sep 26, 2023
Resolves #352. See also the related spec change for the Private Aggregation API: patcg-individual-drafts/private-aggregation-api#98. See also the corresponding ARA explainer change: #1031.
Reopening to capture that we may change the padding scheme to be more direct in the future |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The length of the payload's plaintext may inadvertently reveal details about its contents (e.g. the number of contributions). To protect against leaking this through the encrypted payload, we may want to pad the plaintext to a fixed size.
The text was updated successfully, but these errors were encountered: