Conversation
jeanniekidd
approved these changes
Jun 12, 2020
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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 is the first step in the signature verification process as outlined in ISO_IEC_9796-2_2010 section 7.3.2 -- i.e. "Signature opening"
The output is what's referred to throughout the spec as the "recovered message representative F*". This recovered message representative can then be used to recover the recoverable part of the message M1* detailed in section 7.3.3 -- i.e. "Message recovery". The message recovery/assembly will be done outside of this openssl package, because it is proprietary in nature and very specific to the "Digital signature scheme 1" detailed in section 8.4 of the spec.