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

Unsoundness notice for gix-attributes (kstring integration) #2027

Merged

Conversation

EliahKagan
Copy link
Contributor

@EliahKagan EliahKagan commented Jul 24, 2024

gix-attributes was found by @ssbr to be unsound, as reported in GitoxideLabs/gitoxide#1460. This adds an informational notice for that, as discussed in comments there (cc @Byron).

The text of the notice is taken from that issue (083656c), with slight modification (1a50df1).

It looks like the affected code, having been introduced in GitoxideLabs/gitoxide#400, was most likely present in all published versions of the crate prior to the fix in 0.22.3 (which was one of the bugs fixed in GitoxideLabs/gitoxide#1462). So I have not specified a minimum affected version.

EliahKagan and others added 2 commits July 24, 2024 19:01
gix-attributes was found by @ssbr to be unsound, as reported in
GitoxideLabs/gitoxide#1460. This adds an
informational notice for that, as discussed in comments there.

It looks like the affected code, having been introduced in
GitoxideLabs/gitoxide#400, was present in all
versions of the crate prior to the fix in 0.22.3 (which was one of
the bugs fixed in GitoxideLabs/gitoxide#1462).

Co-authored-by: Devin Jeanpierre <[email protected]>
This makes some minor changes to the advisory description to adapt
the text from GitoxideLabs/gitoxide#1460 to be
an advisory. For the most part it has remained the same. Changes:

* Express the claim of unsoundness with more confidence, since it
  has been reviewed by the maintainer.

* Modify the link to the affected code to point to the latest tag
  for gix-attributes that has that code. The original link was to
  a branch, so it was broken when the fix was applied.

* Apply inline code formatting in a few more places, where doing
  so improves stylistic consistency.
@Shnatsel
Copy link
Member

Thank you! Looks good to me.

To clarify, why is this a draft? Is there anything else you want to do before we merge this?

@Shnatsel
Copy link
Member

Looks good and I see the maintainer is on board. Merging. Thank you!

@Shnatsel Shnatsel merged commit 884aaa1 into rustsec:main Jul 24, 2024
1 check passed
@EliahKagan
Copy link
Contributor Author

[...] To clarify, why is this a draft? [...]

I think it didn't need to be a draft -- I had it as a draft while I was looking over the PR text and checking CI results.

Looks good and I see the maintainer is on board. Merging. Thank you!

Thanks for the very quick response! 😄

@EliahKagan EliahKagan deleted the gix-attributes-unsound-kstring-integration branch July 24, 2024 23:36
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