You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+7-3Lines changed: 7 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,6 +1,8 @@
1
-
# binja_coolsigmaker
1
+
# binja_coolsigmaker (stable channel)
2
2
3
-
(**I apologize for the inconvenience, but due to a breaking change in the binaryninja crate, you will need to make a change to the entry point depending on which branch you build for.**)
3
+
(**The dev branch now contains the version of the plugin for the binja development update channel.**)
4
+
5
+
(**master/main will target stable.**)
4
6
5
7
We all know signature scanning can be extremely useful. Sadly, the two public offerings for Binja are either very slow, or crash extremely often.
6
8
@@ -37,4 +39,6 @@ This project requires the nightly channel of Rust.
37
39
38
40
Check the blog post above for a step-by-step.
39
41
40
-
Check the Cargo.toml file and adjust the `binaryninja` dependency so it points to whatever Binja update channel you want to compile for. __!MAKE SURE!__ Cargo caught your change of branch. It sometimes doesn't realize you changed it. Delete `Cargo.lock` to make Cargo realize you did. Otherwise, it'll keep using whatever version was selected when you built or rust-analyzer ran.
42
+
Checkout the branch of the repository matching the channel of binja you are building for.
// TODO: (maybe) if signature not found, maybe go back a few instructions and attempt to create a signature with an offset.
1007
993
// TODO: introduce a setting for "dumb" searches, where we also search non-executable segments for uniqueness, incase the user doesn't want to check the segments before scanning them.
0 commit comments