MozillaSecurity / MozillaSecurity/FuzzManager
Profile signature match performance
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 208
- Forks
- 48
- Avg merge
- 23h 5m
- Merged PRs (30d)
- 2
Description
Signature performance can vary wildly depending on the symptoms used. Eg. adding a loose crash-address symptom in addition to a symptom to string match on stderr will speed up matching significantly.
It would be great to have a performance counter for each signature, so we have some indication of which signatures could use tuning to improve match performance.
Contributor guide
No contributing guide indexed for this repository
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 locating the signature-matching entry point and the reporting path; neither is named in the issue. Use the loose crash-address and stderr string-match examples to compare timings, then define how a per-signature performance counter is exposed and what result indicates that tuning is needed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- performance
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100