Vector35 / Vector35/binaryninja-api
Difficult to distinguish if byte in string is already escaped or was escaped by BinaryNinja
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 1.3k
- Forks
- 298
- Avg merge
- 5d 5h
- Merged PRs (30d)
- 19
Description
What is the feature you'd like to have?
I'm digging through a blob of partially compressed, poorly obfuscated data, encoded as a hex string in a format which happens to exactly mirror how we escape invalid bytes in strings, which is making it very difficult to figure out what's going on.
There is nuance if you manually count the amount of backslashes, but I can very easily send you 50 examples where that is still ambiguous.
Emitting non ascii string members and other escapees with a differently colored Token would help make things much more clear
Are any alternative solutions acceptable?
Can't think of any others
Additional Information:
Please add any other context or screenshots that would help us understand your feature request here.
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
No file, test, or entry point is named in the issue. Start by locating the Token handling for non-ASCII string members and escape sequences, then determine where their rendering colors are assigned. Done means escaped bytes can be visually distinguished from bytes escaped by Binary Ninja, including ambiguous examples.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- reverse-engineering
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100