Skip to content

Conversation

@mattsb42-aws
Copy link
Contributor

If an invalid signature is passed to sigdecode_string, an AssertionError is raise.
This assertion error was being passed up through CryptographyECKey.verify, rather
than CryptographyECKey.verify catching the error and returning False, as required
by the Key.verify API.

NOTE: This fixes the pyca/cryptography backend isolation tests, but the base and compatibility test runs are still expected to fail.

If an invalid signature is passed to sigdecode_string, an AssertionError is raise.
This assertion error was being passed up through CryptographyECKey.verify, rather
than CryptographyECKey.verify catching the error and returning False, as required
by the Key.verify API.
@mattsb42-aws
Copy link
Contributor Author

Closing in favor of #117 as it removes the need for this.

@mattsb42-aws mattsb42-aws deleted the pyca-ec-verify branch December 27, 2018 22:59
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.

1 participant