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

Increase Ciphertext size limit #272

Closed
wangshan opened this issue Jun 15, 2022 · 3 comments
Closed

Increase Ciphertext size limit #272

wangshan opened this issue Jun 15, 2022 · 3 comments

Comments

@wangshan
Copy link
Contributor

Current HPKE Ciphertext size is limited to 2 bytes, about 65KB, many use cases will need more than this, Prio for eg. doesn't have this limit. Can we change this to 4 bytes so the size can be <1..2^32-1>?

struct {
  HpkeConfigId config_id;    // config ID
  opaque enc<1..2^16-1>;     // encapsulated HPKE key
  opaque payload<1..2^16-1>; // ciphertext
} HpkeCiphertext;
@chris-wood
Copy link
Collaborator

chris-wood commented Jun 23, 2022

@wangshan I'm not opposed to bumping this limit since it's a painless change, but what use cases would require individual reports to contain more than 65KB of data? Could you please propose a PR that lifts the limit from 2^16 to 2^32?

@wangshan
Copy link
Contributor Author

@chris-wood will do.
Use case wise, 65KB can only represent 4B int vector of 16K dimension, if we encode correlations in individual reports then it can easily be breached, for eg. if I want to see histogram of errors by locales, let's say I have 100 error codes and 200 locales, that's already 20K dimension in one hot encoding.

wangshan added a commit to wangshan/draft-ietf-ppm-dap that referenced this issue Jun 24, 2022
@wangshan
Copy link
Contributor Author

PR created: #279

chris-wood pushed a commit that referenced this issue Aug 2, 2022
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

No branches or pull requests

2 participants