Vector35 / Vector35/binaryninja-api
String detection for __oslogstring
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?
BN can automatically detect and define strings in __TEXT.__cstring or __TEXT.__ustring, but ignores in __TEXT.__oslogstring, i think it should parse it as well. Or may be BN should parse all the sections in macho with S_CSTRING_LITERALS type.
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 Mach-O string-detection entry point and compare handling for __TEXT.__cstring and __TEXT.__ustring with __TEXT.__oslogstring. Check how sections marked S_CSTRING_LITERALS are represented, then verify that the chosen scope detects the expected strings without affecting unrelated sections.
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
- Mostly clear
- Newbie friendliness
- 35/100