Mathieu Tarral
Mathieu Tarral
After kAFL 6.0 upgrade https://github.com/IntelLabs/kAFL/pull/178, Nyx-testing hangs on our kAFL runner 
This ticket explores what's the status of implementing the Nyx hypercall API via the VMware port IO backdoor. # kAFL agent On the guest side, in [`libnyx_agent.c`](https://github.com/IntelLabs/kafl.targets/blob/master/linux-user/libnyx_agent/src/nyx_agent.c#L117), there is a...
The goal of this issue is to spark the discussion on the current state of kAFL compared to the [Nyx project](https://github.com/nyx-fuzz), how we might want to align kAFL to match...
The kAFL [`stable-v0.5`](https://github.com/IntelLabs/kAFL/tree/stable-v0.5) branch was established to get a stable pinned version of kAFL for the ccc repo. However, even if the ccc repo's [`requirements.yml`](https://github.com/intel/ccc-linux-guest-hardening/blob/master/deploy/requirements.yml#L5) refers to this branch, the...
Replace [nyx_packer](https://github.com/IntelLabs/kAFL/tree/master/deploy/intellabs/kafl/roles/nyx_packer) role by [vmcall](https://github.com/IntelLabs/kafl.targets/tree/master/linux-user/vmcall) tooling. Only used by ccc-linux-guest-hardening [bkc](https://github.com/intel/ccc-linux-guest-hardening/blob/master/deploy/roles/bkc/meta/main.yml#L15) role https://github.com/intel/ccc-linux-guest-hardening/blob/master/deploy/roles/bkc/meta/main.yml#L15
When starting kAFL, QEMU might complain that some requested features are not supported in messages such as this one ~~~ qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.xxxxx [bit x]...
Hi ! I'm considering using your crate to use a "standard" definition of x86 registers in my project. My goal is to do Virtual Machine Introspection (VMI), and I would...
Use the new Rekall python3 compatible and removes the need for calling `get_symbols`. Currently blocked by this issue on rekall : https://github.com/google/rekall/issues/310#issuecomment-350344454
# Problem 1 : an API to access the syscall arguments We need to design a API on top of the `Sycall` object that we are building from a `Nitro`...
As the new `syscall_parameters` branch allows a read/write access to the syscall's arguments, i tried to read every arguments and write them back while in a callback. It works fine...