polytracker
polytracker copied to clipboard
An LLVM-based instrumentation tool for universal taint tracking, dataflow analysis, and tracing.
>Yeah, I don't expect any cross-architecture build are necessary. Just making it possible to build on both x86 and arm64 would be good. I also don't think this has to...
There is no explicit handling of the `select` IR instruction. That is needed to capture that a tainted condition affects control flow. Taint will likely be propagated through the `select`...
Polytracker's `docker` command adds the external dependencies, maintenance weight and arguably adds very little utility compared to using bare docker CLI commands. Maybe we should get rid of the polytracker...
Moving `#include taintdag/labels.h` in [here](https://github.com/trailofbits/polytracker/blob/master/unittests/src/taintdag/tdag.cpp#L1-L8) like ```c #include #include "taintdag/outputfile.h" #include "taintdag/section.h" #include "taintdag/storage.h" #include "taintdag/string_table.h" #include "taintdag/taint_source.h" #include "taintdag/labels.h" ``` to ```c #include #include "taintdag/labels.h" #include "taintdag/outputfile.h" #include "taintdag/section.h"...
[lunasvg](https://github.com/sammycage/lunasvg) is a simple C++ svg parser and rendering library that we've encountered function tracing [issues](https://github.com/trailofbits/polytracker/issues/6534) in v3.0.1. It might be a good idea to include this codebase in integration...
We currently run unit tests as well as a couple of the example Dockerfiles in CI, but this existing coverage does not seem to cover all Polytracker commands. Some features...
If an application exits due to an assert (or otherwise unexpected exit). The size fields for each section remains at it's [allocated size](https://github.com/trailofbits/polytracker/blob/master/polytracker/include/taintdag/outputfile.h#L100). Under normal circumstances, [that size is updated...
`printf` writes to `stdout` are not captured as taint sinks when running PolyTracker with `POLYTRACKER_STDOUT_SINK=1`. It would be convenient to be able to capture: ```c++ printf("Tainted value: %x", tainted_value); ```...
Joe and I broke down updating things (while the move away from polytracker-llvm is in progress) to dependencies that are compatible with Apple silicon _as well as_ amd64 (Linux, Intel...
This seems like it should be two tests (server, client) with a local fixture to set up the common code. I would use parametrize for tests that share ~90% of...