Oliver Schranz
Oliver Schranz
Since #10 is resolved, we could have multiple instrumentation passes per module, which better fits our definition of modules as self-contained functionality b/c it is not required anymore to split...
We are right now using two different formats for method signatures: For the injection framework TODO, we use the JVM notation, e.g. `Lsaarland/cispa/artist/codelib/CodeLib;traceLog()V`, while for the definition of method filters,...
The current implementation of ```ArtUtils::InjectMethodCall``` assumes all invoked methods to be part of the codelib. Hence, trying to inject a non-Codelib method call results in crashes since the 'symbols' (method...
Forgot this in yesterday's PR #1: makefiles for x86 and x64 that build, deploy and run the fuzzer. As for PR #1: tested on rooted x86 and x64 Pixel 2...
Until now, we either use ArtistGui to instrument apps, or we deploy ARTist as the system compiler in a custom AOSP build to instrument `boot.oat/art`(AOSP compile time), the systemserver and...
When updating the constraint-layout dependency from 1.0.2 to 1.1.2 and importing a module into ArtistGui, the module is not always shown when tapping on an app. While the list of...
Given that we have ready-made ARTist versions at https://github.com/Project-ARTist/ARTist/releases, it would be nice to directly download the correct ARTist version into ArtistGui instead of requiring it to be compiled into...
`chmod`'ing everything to 777 is an obsolete and dangerous relic from the early times of the project where it was all about getting things done quickly. Now that we want...
Before we delete the original oat when recompiling an app, we probe its user and group to later be able to set those accordingly for the freshly compiled, new oat...
We mainly work on Nexus and Pixel devices where oat files are stored in the same location. Other vendors might have changed the folder structure, hence we should test whether...