Skip to content

Conversation

@tomato42
Copy link
Member

@tomato42 tomato42 commented Dec 14, 2020

since both __coords and __precompute have a "final" state, we can easily
implement lock-less handling of those parameters by depending on GIL
(the atomicity of single bytecode instructions)

fixes #238
closes #239 (this in an alternative, simpler approach)

@tomato42 tomato42 added the bug unintended behaviour in ecdsa code label Dec 14, 2020
@tomato42 tomato42 added this to the v0.17.0 milestone Dec 14, 2020
@tomato42 tomato42 self-assigned this Dec 14, 2020
@tomato42 tomato42 force-pushed the less_locking branch 2 times, most recently from f3b636a to 34bbda8 Compare December 14, 2020 09:45
since both __coords and __precompute have a "final" state, we can easily
implement lock-less handling of those parameters by depending on GIL
(the atomicity of single bytecode instructions)
Copy link

@The-Mule The-Mule left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Everything seems to be sane and tested too. r+

@tomato42 tomato42 merged commit 4e059b9 into tlsfuzzer:master Dec 17, 2020
@tomato42 tomato42 deleted the less_locking branch December 17, 2020 16:55
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

bug unintended behaviour in ecdsa code

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Killing long computation in IPython with Ctrl+C sometimes leaves the environment inoperable

2 participants