Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Differenciate between tainting analysis and symbolic execution #4

Closed
0ca opened this issue Aug 30, 2016 · 2 comments
Closed

Differenciate between tainting analysis and symbolic execution #4

0ca opened this issue Aug 30, 2016 · 2 comments
Milestone

Comments

@0ca
Copy link
Collaborator

0ca commented Aug 30, 2016

The plugin could be use just to do tainting analysis and know which instructions of the program are tainted and this is different to make a symbolic execution analysis where all the formulas (from the tainted instructions) are being generated.

Tainting analysis should be quite more light than symbolic execution. So in some scenarios it could be useful to allow the user just to do tainting without symbolic.

@0ca
Copy link
Collaborator Author

0ca commented Aug 31, 2016

I added two flags in globals.cpp:

#define ENABLE_TAINTING_ENGINE true
#define ENABLE_SYMBOLIC_ENGINE true

But when I disable the symbolic engine the tainting engine is not working. I reported this "bug" to triton:
JonathanSalwan/Triton#379

@0ca
Copy link
Collaborator Author

0ca commented Sep 6, 2016

Jonathan fixed it:
JonathanSalwan/Triton#379

Now it is possible to disable the symbolic engine and do only taint analysis.

@0ca 0ca closed this as completed Sep 6, 2016
@0ca 0ca modified the milestone: v0.1 Sep 8, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant