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

Is this an implementation of Boneh, Drijvers, Neven or otherwise secure against a rogue public-key attack? #10

Open
SaleProperly opened this issue Jul 1, 2019 · 2 comments

Comments

@SaleProperly
Copy link

I know there is a BLS multisig scheme where a common message can be signed and it is secure against a rogue public-key attack see https://crypto.stanford.edu/~dabo/pubs/papers/BLSmultisig.html

Is this an implementation of that or do additional precautions need to be taken when signing a common message?

@meyer9
Copy link
Member

meyer9 commented Aug 10, 2019

Make sure when aggregating keys that you have confirmed that users have access to the private key corresponding to the public key. This can be done by having them sign their own public key.

@SaleProperly
Copy link
Author

I thought that might be the case, but I wanted to double check. Thanks.

Perhaps this should be made clearer elsewhere for others who might not know better? Or is it already mentioned somewhere?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants