Vector35 / Vector35/binaryninja-api
Find in Selected Range
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 have two pieces of information: a YARA search result for a small stretch of bytes and I have a small set of bytes that represent the start of the function that typically contains the YARA result hex string in other samples. Finding the general location where the YARA result is located using the find hex string or the advanced binary search is awesome for locating the general area. But then the second set of instrucitons are hard to find without doing a bounded find with a search range that only shows around where you are looking. If the bytes that you know start a function are super common, making a new find will find too many locations. Find does have a custom search range, but it must be populated manually.
It would be super awesome if the range of bytes that I have selected in view area automagically populated as the start and end addresses in the find dialog's custom search range. My recommendation would be to add a second type of "Find" in the "Edit" menu called "Find In Selected" or some such. And the resulting Find dialog would be automatically set to a custom range populated with the start and end address of the selected bytes in the GUI. This find should have a keyboard shortcut (or I can make a custom one) to make this as smooth as possible.
Is your feature request related to a problem?
Tedious to copy and paste start and end somewhere else and then copy and paste them into the Find dialog.
Additional Information:
Here I have searched for the YARA string: 410fbaf01f 4181f8e69cca1c
Now I want to search for this:
Like this:
And arrive 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
Start with the existing Find dialog's custom search range and the Edit menu behavior described in the issue. Trace how a selected byte range can populate the dialog's start and end addresses, then verify that a Find In Selected action and shortcut search only within that range without manual copying.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- desktop, reverse-engineering
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100