Automated search for runtime-loaded libraries
Open
Nobody has claimed this yet.
enhancement
priority-low
- Dominant language
- Rust
- Stars
- 2.7k
- Forks
- 144
- Avg merge
- 12h 21m
- Merged PRs (30d)
- 146
Description
Related to #765, @CvvT pointed out that we should (more generally) search for more runtime-loaded libraries, similar to libgcc_s.so.1.
I think there is no harm in conservatively over-approximating (modulo some minor one-time perf hit due to rewriter overhead) to just pull in any .so-like strings we notice that also exist on the system.
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
Start by reading related issue #765 and tracing the rewriter path mentioned here. Investigate how runtime-loaded libraries such as libgcc_s.so.1 are discovered, then verify that .so-like strings found by the rewriter are checked against libraries present on the system without unnecessary additions.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- operating-systems
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100