Skip to content
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

Fix/rustsec 2025 0009 0.17 #193

Merged
merged 2 commits into from
Mar 12, 2025
Merged

Conversation

chifflier
Copy link
Member

Update oid-registry to 0.8.1 (fix CI build)
Upgrade ring to version >= 0.17.2. (#190 - RUSTSEC-2025-0009)

@chifflier chifflier requested a review from cpu March 12, 2025 09:00
@@ -436,7 +436,7 @@ impl<'a> TbsCertificate<'a> {
pub fn inhibit_anypolicy(
&self,
) -> Result<Option<BasicExtension<&InhibitAnyPolicy>>, X509Error> {
self.get_extension_unique(&OID_X509_EXT_INHIBITANT_ANY_POLICY)?
self.get_extension_unique(&OID_X509_EXT_INHIBIT_ANY_POLICY)?
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm confused what happened here, I fixed this instance, and the one in src/extensions/mod.rs already in 27dd7d2 no? Did that work get undone?

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Oh! I see now, this PR is targetting a x509-parser-0.17 feature branch 💡

In that case maybe next time it'd be better to cherry-pick the equivalent fixes from master where possible?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Indeed, sorry I should have added it in the description.
I just created the x509-parser-0.17 branch to backport fixes (like this one). We can of course also cherry-pick any change that is interesting for this branch.

This is also in anticipation of some future breaking changes when this crate will have to be updated to the next asn1-rs releases (which have a lot of pending breaking changes in its API, and will require adjusting x509-parser). Of course the goal is to make the update as easy as possible.

CHANGELOG.md Outdated
### Added/Changed/Fixed

Global:
- Upgrade `ring` to version >= 0.17.2. (#190 - RUSTSEC-2025-0009)
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This should be .12:

Suggested change
- Upgrade `ring` to version >= 0.17.2. (#190 - RUSTSEC-2025-0009)
- Upgrade `ring` to version >= 0.17.12. (#190 - RUSTSEC-2025-0009)

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

(Also in the PR description)

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

oh, good catch thanks!
I force-pushed an updated version

@chifflier chifflier force-pushed the fix/rustsec-2025-0009-0.17 branch from 9a5dd80 to 8099dc0 Compare March 12, 2025 13:43
@chifflier chifflier requested a review from cpu March 12, 2025 13:45
@chifflier chifflier merged commit 7066832 into x509-parser-0.17 Mar 12, 2025
34 checks passed
@chifflier chifflier deleted the fix/rustsec-2025-0009-0.17 branch March 12, 2025 13:55
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants