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

Add check for the dkg public key after resharing #491

Closed
wants to merge 2 commits into from

Conversation

leetingo
Copy link

@leetingo leetingo commented Jun 30, 2023

Check whether the DKG public key changes before and after resharing among the same group of nodes.

Closes #489

@CLAassistant
Copy link

CLAassistant commented Jun 30, 2023

CLA assistant check
All committers have signed the CLA.

@github-actions
Copy link

🔒 Could not start CI tests due to missing safe PR label. Please contact a DEDIS maintainer.

@ineiti ineiti added the safe PR label Jul 3, 2023
@ineiti
Copy link
Member

ineiti commented Jul 3, 2023

Please add a description in the PR.

@leetingo
Copy link
Author

leetingo commented Jul 4, 2023

Added.

@ineiti
Copy link
Member

ineiti commented Jul 4, 2023

And you need to sign the CLA, if I read the failing tests correctly...

@pierluca
Copy link
Contributor

In particular, regarding the CLA, it seems the e-mail/username you used as part of your commit (litiange) is not associated with your GitHub account. This is why the CLA automation can't detect whether you've signed it already or not.

@@ -667,6 +667,10 @@ func TestDKGResharing(t *testing.T) {
newSecret, err := share.RecoverSecret(suite, newSShares, thr, defaultN)
require.NoError(t, err)
require.Equal(t, oldSecret.String(), newSecret.String())
// 3.
for i := 0; i < len(dkgs); i++ {
require.Equal(t, shares[i].Public(), newShares[i].Public())
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

the overall DKG public key should remain constant, not the public key of each share, right ?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

That's correct, but the Public() method returns the public key of the distributed key:

// Public returns the public key associated with the distributed private key.

So this should pass.

@K1li4nL
Copy link
Contributor

K1li4nL commented Sep 4, 2024

As stated in the related issue, this check has been added when we merged DRAND version of this pedersen dkg, thanks for your work !

@K1li4nL K1li4nL closed this Sep 4, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

DKG Protocol - Public Key Change After Reshare
6 participants