Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I created a small sample to play with ripr. The analyzed binary is based on this RC4 code:
https://gist.github.com/rverton/a44fc8ca67ab9ec32089
I added a static XOR step to make it a "non-standard" implementation and to see how static obfuscation keys can be handled by ripr.
My goal is to do a writeup based on this experiment, to document the process of using ripr to create standalone implementations of custom obfuscators/crypto. At the current state the ripr code successfully replicates the output of the original binary, but I wonder if the authors can add their comments to highlight some best practices, easier/better solutions.