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

discussions on rogue key attacks #10

Open
zhenfeizhang opened this issue Mar 18, 2019 · 0 comments
Open

discussions on rogue key attacks #10

zhenfeizhang opened this issue Mar 18, 2019 · 0 comments
Labels
help wanted Extra attention is needed

Comments

@zhenfeizhang
Copy link
Collaborator

zhenfeizhang commented Mar 18, 2019

See Dan's post on the attack and potential defenses.

Summary of defense mechanisms:

  • proof of possession: before the signatures under the public key can be used in aggregation, the signer has to provide proof of possession of the secret key. e.g. the signer can provide a signature of the public key under the secret key.
  • always sign different messages: by including into the message that needs to be signed with a public key.
  • Use BLS+ variant.

The current draft does not enforce any of above methods.

To discuss:

  • whether to add some/all the defense mechanisms in the draft
    • a related question: what are the best use cases for each method
  • if there is a reason (not) to mandate a mechanism

We're considering various use-cases for use in:

  • PKI
  • Blockchain transactions
  • Multisig applications
@zhenfeizhang zhenfeizhang added the help wanted Extra attention is needed label Mar 18, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
help wanted Extra attention is needed
Projects
None yet
Development

No branches or pull requests

1 participant