Jefferson Cesar Antunes
Systems developer · Linux/OpenBSD process introspection and memory analysis
I'm self-taught. Most of what I know comes from reading man pages, breaking things in VMs, and tracing syscalls until the behavior made sense.
I write small C and Bash tools that I can read end to end. My interest is the boundary where abstractions stop helping: process state, memory layout, and what the kernel will and won't tell you.
PMV started because I wanted to know which OpenBSD processes had actually
called pledge(2), not which ones were supposed to. K-Scanner came from the
same question on Linux: which mappings are really writable and executable
right now.
| Project | What it does | Language |
|---|---|---|
| PMV | OpenBSD process mitigation viewer. Reads kinfo_proc through kvm(3) and reports whether pledge(2), unveil(2), and W^X are active per process. Reports presence, not policy depth, because that is all the kernel exposes. |
C11 |
| K-Scanner | Linux RWX memory scanner. Parses /proc/[PID]/maps, flags writable and executable regions, and separates JIT mappings from suspicious ones. |
C99 |
Both build with make. Each repository documents what it can and cannot
detect.
- Adding
make verify, behavioral tests, and a benchmark to both repositories. - Documenting the detection limits of each tool, and why they exist.
- Testing on OpenBSD 7.9 and Arch Linux; experiments run in VMs.
C (C99/C11), Bash, Python · OpenBSD, Arch Linux · Neovim
If a tool here overclaims or fails on your machine, open an issue with the command, your OS and kernel version, and the output. A reproducible report is more useful to me than a feature request.