ida-explorer: verify that the cache key is unique enough
Open
Nobody has claimed this yet.
enhancement
ida-explorer
- Dominant language
- Python
- Stars
- 6.2k
- Forks
- 726
- Avg merge
- 11d 11h
- Merged PRs (30d)
- 7
Description
https://github.com/mandiant/capa/blob/430f9da449cbd2c7142594f3bcf370cbcfee37d8/capa/ida/plugin/cache.py#L40
https://github.com/mandiant/capa/blob/430f9da449cbd2c7142594f3bcf370cbcfee37d8/capa/ida/plugin/cache.py#L46
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 with capa/ida/plugin/cache.py at lines 40 and 46, then trace where the cache key is constructed and consumed by the IDA Explorer plugin. Determine which inputs distinguish cached results and document or test whether different relevant inputs can collide; the issue is done when the key's uniqueness is verified or a specific collision is addressed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- reverse-engineering, tooling
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100