Atualização para suporte da nova versão signxml #355
Merged
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
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.
signxml recebeu uma nova versão (4.0) o qual substituíram internamente o PyOpenSSL pelo Cryptography, no entanto isso acusou incompatibilidade com algumas parte do código:
-----BEGIN CERTIFICATE-----e-----END CERTIFICATE-----pois eles são usados para validar o inicio e fim do certificado, que agora possui um throw dentro do código quando não encontra as tags: XML-Security/signxml@b42c093Obs: Favor fazer Squash and Merge para evitar merge dos commits de teste realizados.