Update "baseline" test vectors (no optional features) #183
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
aljones15
approved these changes
Jul 21, 2024
dlongley
approved these changes
Jul 21, 2024
…aft 06 updates. Only cryptographic value changes. No API/procedure/textual changes.
msporny
force-pushed
the
test-vector-update
branch
from
02f2012 to
b747f62
Compare
msporny
approved these changes
Aug 16, 2024
|
Informative update only, multiple reviews, changes requested and made, no objections, merging. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR is in response to issue #181. It updates the "baseline" BBS test vectors but does not update the optional feature test vectors. This update brings the test vectors in line with version 06 of the IETF BBS Signature Scheme draft. Optional feature test vectors will be updated in a separate PR.
These updates result only in cryptographic value changes in the separate text vector files which are imported into the specification via the ReSpec
data-includemechanism. No API, procedure, textual, or formatting changes are included. Test vectors are non-normative.Preview | Diff