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

Separate aux data generation and key refresh protocols #111

Closed
fjarri opened this issue Apr 3, 2024 · 1 comment
Closed

Separate aux data generation and key refresh protocols #111

fjarri opened this issue Apr 3, 2024 · 1 comment
Labels
API Involves backwards-incompatible changes of the public API enhancement New feature or request
Milestone

Comments

@fjarri
Copy link
Member

fjarri commented Apr 3, 2024

While the question in #98 remains open, we can certainly implement a light version of it: separate the aux data generation and the key refresh, so that the user could choose how often to perform them independently. Aux data generation needs to generate primes, so it's relatively slow, but perhaps it can be done less often than key refresh.

@fjarri fjarri added enhancement New feature or request API Involves backwards-incompatible changes of the public API labels Apr 3, 2024
@fjarri fjarri added this to the v1.0.0 milestone Apr 3, 2024
@fjarri
Copy link
Member Author

fjarri commented May 24, 2024

AuxGen was separated in #119, to be used in the threshold scenario. We cannot use CGGMP's KeyRefresh for it, and will probably have to adapt KeyResharing, so providing a separate KeyRefresh is not necessary for now.

@fjarri fjarri closed this as completed May 24, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
API Involves backwards-incompatible changes of the public API enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant