Skip to content

ed25519 tests, perf test fix, dkim_free() memory leak, dkim_sig_keybits() #243

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

Open
wants to merge 1 commit into
base: develop
Choose a base branch
from

Conversation

jcastle-gh
Copy link

Add 4 ed25519 directed tests and 2 ed25519 performance test scripts. In the Makefile t-cleanup is not part of $check_PROGRAMS anymore so that it can can be run after the $check_SCRIPTS tests instead of before them, allowing those tests to use the keyfile that t-cleanup deletes.

Also fix 3 bugs found while doing the above.

  1. The t-signperf and t-verifyperf performance tests were blindly looping on sign and verify operations without checking for correct results. They always reported "pass" even when the operation failed, for example when the key was not found. Now they assert the results and "fail" if something goes wrong.

  2. In dkim_free() the ed25519 crypto structure wasn't getting freed.

  3. In dkim_sig_keybits() the wrong size was being returned for ed25519. For now, always return 256 since ed25519 is always 256-bit. The underlying bug is in the calculation of 'keybits' in various other dkim functions and that will be fixed in a subesquent PR.

…ts()

Add 4 ed25519 directed tests and 2 ed25519 performance test scripts. In
the Makefile t-cleanup is not part of $check_PROGRAMS anymore so that it
can can be run after the $check_SCRIPTS tests instead of before them,
allowing those tests to use the keyfile that t-cleanup deletes.

Also fix 3 bugs found while doing the above.

1. The t-signperf and t-verifyperf performance tests were blindly
   looping on sign and verify operations without checking for correct
   results. They always reported "pass" even when the operation failed,
   for example when the key was not found. Now they assert the results
   and "fail" if something goes wrong.

2. In dkim_free() the ed25519 crypto structure wasn't getting freed.

3. In dkim_sig_keybits() the wrong size was being returned for ed25519.
   For now, always return 256 since ed25519 is always 256-bit.  The
   underlying bug is in the calculation of 'keybits' in various other
   dkim functions and that will be fixed in a subesquent PR.
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