Feature: guid from various encodings
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 6.2k
- Forks
- 726
- Avg merge
- 11d 11h
- Merged PRs (30d)
- 7
Description
Due to the number of variations that could exist.
thoughts on a guid: {....} feature that expands into various ways of encoding it?
pro: makes it easier for rule authors
pro: could hook into an encyclopedia of GUIDs to enable use of symbolic names, too
con: single feature would expand into multiple features to support this, which could be complex to implement/display (think about single string reference vs bunch of immediate constants).
Originally posted by @williballenthin in https://github.com/fireeye/capa-rules/issues/183#issuecomment-730618016
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
No implementation files or tests are identified. Review the original discussion in capa-rules issue #183, then define the supported GUID encodings and whether symbolic names are in scope; the work is done when that design is agreed and the feature's implementation and display behavior are specified.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- reverse-engineering
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100