Compile-time flags for signature methods #17
Conversation
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
1 participant
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.
As I had problems to compile this lib with my xmlsec1 version (missing MD5 methods) I introduced compile-time flags to disable unavailable signature methods.
This is done by probing each signature method by compiling a test snipped.
If the compilation succeeds, the flag for this signature method is enabled.
Alternatively we could also generate the
XmlSecSignatureMethodenum andto_methodmethod in thebingings.rs.I also added all entries for the current crypto.h in the xmlsec1 repo.