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

Test case P-384/P-521 bug from golang #66

Closed
alex opened this issue Jan 23, 2019 · 5 comments
Closed

Test case P-384/P-521 bug from golang #66

alex opened this issue Jan 23, 2019 · 5 comments

Comments

@alex
Copy link
Contributor

alex commented Jan 23, 2019

golang/go#29903, but no test case there :-) Hopefully one part of Google can talk to another.

@thaidn
Copy link
Contributor

thaidn commented Jan 23, 2019

We have some logistic problem. Once it's resolved we'll publish the relevant test cases.

@alex
Copy link
Contributor Author

alex commented Jan 24, 2019

Awesome.

At the time I filed this I didn't even realize your team had found the bug, but chatting with Fillippo I gather the test case came from your work :-)

@thaidn
Copy link
Contributor

thaidn commented Jan 24, 2019

Yeah the test case came from this project. Daniel Bleichenbacher created the test case, and another person ran it against Golang and found the bug.

@bleichen
Copy link
Contributor

One issue here is that it took me some time to notice that there is already a published paper on the
attack. The golang bug is a special case of this paper.

Akishita T., Takagi T. (2003) Zero-Value Point Attacks on Elliptic Curve Cryptosystem. ISC 2003. LNCS 2851

Instead of just adding test vectors for the golang bug, I'm extending the the test vectors to include test cases for other similar situations, i.e. distinct curves, distinct point representations, distinct addition chains.

@thaidn
Copy link
Contributor

thaidn commented Nov 26, 2019

The test cases that @bleichen mentioned above were added in 7c9c6db.

@thaidn thaidn closed this as completed Nov 26, 2019
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

3 participants