Navigation Menu

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

Bug: invalid G1 and G2 cached in PrivateKey #289

Merged

Conversation

random-zebra
Copy link
Contributor

Introduced in #168.
The copy assignment operator does not invalidate the caches.
This could dangerously lead to situations where a PrivateKey returns wrong G1/G2 elements (if they were cached before the copy).

@wjblanke wjblanke merged commit fe7112f into Chia-Network:main Nov 10, 2021
furszy added a commit to PIVX-Project/bls-signatures that referenced this pull request Nov 26, 2021
183be27 BugFix: Invalidate caches in PrivateKey copy assignment operator (random-zebra)
4272466 QA: test cache invalidation for PrivateKey copy assignment operator (random-zebra)

Pull request description:

  Pretty serious bug in the copy-assignment operator, discovered after a long investigation with @furszy over an intermittent failure in a unit test for deterministic masternodes in Core.

  For reference, pull request submitted upstream: Chia-Network#289

ACKs for top commit:
  furszy:
    obvious ACK 183be27 🤘 .

Tree-SHA512: 2d43ed6bbfb761df889a8b6b563cd5e3ef103632941dcb96220bf6695e881ffccae29e66640bcd32262d2886e4858fc745d373fad413c3a4dcb2a90a3b9a7d0b
UdjinM6 pushed a commit to UdjinM6/bls-signatures that referenced this pull request Dec 1, 2021
* QA: test cache invalidation for PrivateKey copy assignment operator

* BugFix: Invalidate caches in PrivateKey copy assignment operator
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

Successfully merging this pull request may close these issues.

None yet

3 participants