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

Self-contained proof of malicious behavior for Round 3 of KeyGen #103

Open
fjarri opened this issue Jan 30, 2024 · 0 comments · May be fixed by #170
Open

Self-contained proof of malicious behavior for Round 3 of KeyGen #103

fjarri opened this issue Jan 30, 2024 · 0 comments · May be fixed by #170
Assignees
Labels
cryptography Needs cryptographic expertise
Milestone

Comments

@fjarri
Copy link
Member

fjarri commented Jan 30, 2024

Suppose we are running the KeyGen protocol (Fig. 5, or KeyInit in the library terms), and in Round 3, when verifying a message from another node, the Schnorr proof verification didn't pass.

The goal with generating evidence of malicious behavior (#43) is to create a self-contained data blob which would prove for anyone that the owner of the signing key corresponding to some verifying key did something wrong. Which means that it can only contain the publicly available data and the messages from that signer. But the Schnorr proof in question depends on rid, which is assembled from the data sent by all the other nodes. How do we make a self-contained evidence package in this case?

One possibility is that rid is not really necessary - which will eliminate the problem. What kind of an attack will be possible if it is removed for the proof's parameters?

@fjarri fjarri added the cryptography Needs cryptographic expertise label Jan 30, 2024
@fjarri fjarri added this to the v0.2.0 milestone Jan 30, 2024
@fjarri fjarri modified the milestones: v0.2.0, v0.3.0 Oct 26, 2024
@fjarri fjarri self-assigned this Nov 19, 2024
@fjarri fjarri linked a pull request Dec 26, 2024 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
cryptography Needs cryptographic expertise
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant