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

[Spec] =compute the key hash of reporting ID= uses wrong prefix for buyerAndSellerReportingId and buyerReportingId #1085

Open
brusshamilton opened this issue Mar 14, 2024 · 0 comments
Labels
spec Relates to the spec

Comments

@brusshamilton
Copy link
Contributor

=compute the key hash of a reporting ID= always uses "NameReport" as the prefix of the k-anonymity key. When the buyerAndSellerReportingId is used the prefix should be "BuyerAndSellerReportId". Likewise when the buyerReportingId is used the prefix should be "BuyerReportId".

These need to be counted separately because they guard separate fields in reporting. If they were counted together for k-anonymity purposes, additional information could be leaked based on which field was populated.

@JensenPaul JensenPaul added the spec Relates to the spec label Mar 15, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
spec Relates to the spec
Projects
None yet
Development

No branches or pull requests

2 participants