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

Explore changing the way secure channels are implemented in both key refresh protocols #554

Open
becgabri opened this issue Nov 12, 2024 · 0 comments
Labels
crypto enhancement New feature or request security Security or input validation issue

Comments

@becgabri
Copy link

Key refresh in both the n/n and t/n settings require parties to send secret values to one another over a secure channel. In the original version of CGGMP this is done using Paillier encryption. In the updated version, this is done through establishing temporary pairwise DH keys and using them as a one time pad to transmit shares. This is more efficient, as the authors claim in their updated paper, and it makes the proof of security easier.

In the future, we should either look into incorporating the CGGMP change or adding an abstraction for a secure channel such that if two parties share a symmetric key they can simply use it to share these values instead.

@gatoWololo gatoWololo added enhancement New feature or request security Security or input validation issue crypto labels Nov 15, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
crypto enhancement New feature or request security Security or input validation issue
Projects
None yet
Development

No branches or pull requests

2 participants