Skip to content

tolerate NULL params in ECDSA SHA2 AlgorithmIdentifier#9002

Merged
alex merged 2 commits intopyca:mainfrom
reaperhulk:tolerate-bad-certs
Jun 1, 2023
Merged

tolerate NULL params in ECDSA SHA2 AlgorithmIdentifier#9002
alex merged 2 commits intopyca:mainfrom
reaperhulk:tolerate-bad-certs

Conversation

@reaperhulk
Copy link
Copy Markdown
Member

Java 11 does this incorrectly. It was fixed in Java16+ and they are planning to do a backport, but we'll need to tolerate this invalid encoding for a while.

Java 11 does this incorrectly. It was fixed in Java16+ and they are
planning to do a backport, but we'll need to tolerate this invalid
encoding for a while.
Comment thread src/rust/src/x509/certificate.rs Outdated
Comment thread src/rust/src/x509/certificate.rs Outdated
@alex alex merged commit 1355c2e into pyca:main Jun 1, 2023
reaperhulk added a commit to reaperhulk/cryptography that referenced this pull request Jun 1, 2023
* tolerate NULL params in ECDSA SHA2 AlgorithmIdentifier

Java 11 does this incorrectly. It was fixed in Java16+ and they are
planning to do a backport, but we'll need to tolerate this invalid
encoding for a while.

* test both inner and outer
alex pushed a commit that referenced this pull request Jun 1, 2023
* tolerate NULL params in ECDSA SHA2 AlgorithmIdentifier (#9002)

* tolerate NULL params in ECDSA SHA2 AlgorithmIdentifier

Java 11 does this incorrectly. It was fixed in Java16+ and they are
planning to do a backport, but we'll need to tolerate this invalid
encoding for a while.

* test both inner and outer

* changelog entry

* language
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

X.509 certificate parsing error in v41.0.0, not observed in v38.0.4, v40.0.2

2 participants