microsoft / microsoft/rust-symcrypt
Graceful exit for version mismatch
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 72
- Forks
- 15
- Avg merge
- 3d 2h
- Merged PRs (30d)
- 11
Description
Currently if there is a version mismatch ex:
you have symcrypt 103.1 on your machine but check out a future version that has bindings for 103.4 you will error out with a segfault.
Code should instead gracefully exit and alert the user to update their version and to read the documentation.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue names no files, tests, or entry points. Start by reproducing the version mismatch between the installed SymCrypt library and the checked-out bindings, then locate the FFI initialization or version-check path. Done means the mismatch exits without a segmentation fault, tells the user to update SymCrypt, and points them to the documentation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- cryptography
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100