Skip to content

tanton_engine: possible public unsound api #2286

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

Open
wants to merge 5 commits into
base: main
Choose a base branch
from

Conversation

charlesxsh
Copy link

The original github repo seems like got deleted, not sure how to create the PR/issue at the upstream project

@djc
Copy link
Contributor

djc commented Apr 25, 2025

This is the 4th PR you've filed this month (#2262, #2263, #2284). How are you finding these?

Please note the failing CI checks.

@charlesxsh
Copy link
Author

This is the 4th PR you've filed this month (#2262, #2263, #2284). How are you finding these?

Please note the failing CI checks.

Thanks for the notifying. I will fix the linting ASAP. I am working on a research project that can automatically find these issues.

@djc djc changed the title possible public unsound api tanton_engine: possible public unsound api Apr 25, 2025
@charlesxsh
Copy link
Author

Do we have any update/plan on merging these PRs? @djc

@djc
Copy link
Contributor

djc commented May 2, 2025

I sent an email to the maintainer just now, I'm going to wait for 2 weeks before publishing this, per discussion in #1092.

@djc
Copy link
Contributor

djc commented May 2, 2025

Okay, we have approval from the author to publish. I think we want to substantially simplify the advisory, though:

  • Drop the long code samples
  • Use the functions key to highlight (some of) the unsafe functions you've found
  • Provide a high-level description of the issue (like "lack of bound checking")
  • Explicitly mention that this crate no longer appears to be maintained

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