substring/regex support for API
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 6.2k
- Forks
- 726
- Avg merge
- 11d 11h
- Merged PRs (30d)
- 7
Description
### Summary
Allow substring or regex matching for API to allow for more generic rules.
### Motivation
Want to key on something like this regardless of glibc version:
- api: .dynsym.fopen@@glibc_2.2.5
### Describe alternatives you've considered
Could enumerate all glibc versions out there but rule would be expensive and high maintenance.
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 tracing the API matching entry point and how rules represent API names, using the glibc-version example as the target case. Review existing matching behavior and determine how substring or regex semantics should be specified; done means a generic rule can match versioned API names without enumerating every version, with coverage for the chosen behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- reverse-engineering, security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100