We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
When the local environment has a version of pyca/cryptography >= 35.0.0 then ASN.1 parser errors cause the process to fail.
>= 35.0.0
Version 2.0.0 (higher than this currently don't even check the metadata signature - see issue #264)
2.0.0
Certificate provided fails some country-specific encoding when being parsed and currently errors out. It should continue.
Certificate provided should be accepted and used
Unsure. I suspect that a fix similar to what was done with the tooling in this thread is followed: panzi/verify-ehc#21
Output from version 2.0.0 with pyca/cryptography > 35.0.0
> 35.0.0
INFO:pyff.fetch:successfully fetched https://haka.funet.fi/metadata/haka-metadata-v9.xml ERROR:xmlsec:error parsing asn1 value: ParseError { kind: EncodedDefault, location: ["BasicConstraints::ca"] } ERROR:pyff.samlmd:Error parsing https://haka.funet.fi/metadata/haka-metadata-v9.xml: No valid ds:Signature elements found
Output from 2.0.0 with pyca/cryptography 3.4.8 (the last version before the big version number jump to 35.0.0)
3.4.8
INFO:pyff.fetch:successfully fetched https://haka.funet.fi/metadata/haka-metadata-v9.xml
No error, metadata read successfully and entityIDs processed.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
When the local environment has a version of pyca/cryptography
>= 35.0.0
then ASN.1 parser errors cause the process to fail.Code Version
Version
2.0.0
(higher than this currently don't even check the metadata signature - see issue #264)Expected Behavior
Certificate provided fails some country-specific encoding when being parsed and currently errors out. It should continue.
Current Behavior
Certificate provided should be accepted and used
Possible Solution
Unsure. I suspect that a fix similar to what was done with the tooling in this thread is followed:
panzi/verify-ehc#21
Steps to Reproduce
Output from version
2.0.0
with pyca/cryptography> 35.0.0
Output from
2.0.0
with pyca/cryptography3.4.8
(the last version before the big version number jump to 35.0.0)No error, metadata read successfully and entityIDs processed.
The text was updated successfully, but these errors were encountered: