polytracker
polytracker copied to clipboard
trailofbits
An LLVM-based instrumentation tool for universal taint tracking, dataflow analysis, and tracing.
Still very rough and with old/new code mixed. Highlights the main ideas of the section based approach. Test cases for tdag c++ impl won't run due to build problems.
Pairs with https://github.com/trailofbits/polytracker-llvm/pull/13 Needed because Ubuntu-jammy doesn't have python3.8 but has 3.10 instead.
Maybe this shouldn't be prefixed by `ABI_PATH` in a future version. If you specify an ignore list, you could just as well specify the full path to it. It is...
Great! We should probably do a maintenance check to ensure all files have this header. _Originally posted by @hbrodin in https://github.com/trailofbits/polytracker/pull/6473#discussion_r970960636_
In the current implementation fast path, each function entry would have to 1. strlen(function-name) 2. acquire lock 3. lookup function name map (compute hash) 4. return index Couldn't all this...
Decide on a more appropriate abstraction for taint sources. Currently it is file-focused, e.g. the file descriptor is stored along side. However, with the introduction of argv tainting this abstraction...
I tried the following sequence: 1. Build the polytracker image: ```shell $ docker build -t trailofbits/polytracker . ... [+] Building 42.0s (20/20) FINISHED ``` 2. Ceated a new virtual env:...
To allow new developers an easier start we should consider extracting the section https://github.com/trailofbits/polytracker#building-polytracker-from-source into a BUILDING.md. We could then describe the steps in detail (command line examples). Hopefully, that...
Metadata
Owner
Metadata
An LLVM-based instrumentation tool for universal taint tracking, dataflow analysis, and tracing.