-
Notifications
You must be signed in to change notification settings - Fork 421
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
Add support for xmlsec package as backend #886
Labels
Comments
Thank for filling in this issue. I agree that we should look into this. |
Is there anything I can do to help get the ball rolling on this? |
A little late, but I made a fork and PR to hopefully integrate xmlsec better if you want to test it, #961 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Looking through the project history the decision to call out to the xmlsec1 binary made sense at the time due to the poor state of the library. However, the library looks to be in far better state now, with regular updates and a far more usable API, as well as pre-built wheels available for many architectures.
Using the library directly should offer both performance and safety benefits compared to the current setup, in addition to enabling new applications such as lambda/serverless deployments
The text was updated successfully, but these errors were encountered: