[ SECURITYLAB ]

SecurityLab track — runtime and distributed systems, kernel debugging, eBPF, Go concurrency, memory models, bootloaders, and assembly walkthroughs. Code-first, source-cited, mechanism-deep.

Long-form writing and video on runtime, distributed systems, and kernel internals — the layers below the application where most production reliability is actually decided.

Topics: Go runtime and concurrency, distributed systems patterns (RPC, queues, idempotency), kernel debugging with GDB/QEMU, eBPF, memory models, bootloaders, and assembly walkthroughs.

Companion to the HarrisonSecurityLab YouTube channel. Blog and video are listed below — most recent first.

Blog
My Second iPhone Lives at Home. I Use It From Anywhere.

My Second iPhone Lives at Home. I Use It From Anywhere.

I have two numbers in two countries and stopped carrying two phones. The second iPhone stays at home, plugged into a 2016 laptop that pretends to be its Bluetooth keyboard, mouse and headset. I take its calls, answer its WeChat, and open its banking apps from my main phone, anywhere. No jailbreak. Here is how it works, and the five bugs that took the longest.

2026-11-15 8 min read
Blog
Hang Up, and It Rings Once More

Hang Up, and It Rings Once More

My app showed incoming calls for a phone at home through Apple VoIP pushes and CallKit. Decline one, and a split second later it rang again and vanished. The cause is a PushKit rule: every VoIP push must become a reported call. The gateway's 'call ended' push arrived after the app had already ended the call, so the app had to report a call it no longer had. The fix was to stop sending pushes the app did not need.

2026-11-15 7 min read
Blog
The Fix That Brought the Bug Back

The Fix That Brought the Bug Back

The first connection to my phone stream showed nothing for ten seconds and gave up; the second worked instantly. I fixed it by restarting the GPU pipeline to replay a cache. Two days later the bug was back, caused by that fix: a restart storm leaked 500 threads, the GPU stopped starting, the transcoder quietly fell back to a mode without the cache, and a log line that only fired once kept it hidden for 17 hours.

2026-11-15 7 min read
Blog
The Decoder Kept One Frame for Itself

The Decoder Kept One Frame for Itself

A GPU transcoder added 26 ms on average and up to five seconds at the 95th percentile, and only when the screen was nearly still. A hardware H.264 decoder was holding the last frame of every burst until the next one arrived, which on a phone screen can be never. How a replay probe found it, which decoders do it, and what switching cost.

2026-11-15 6 min read
Blog
The Bluetooth Accessory iOS Would Not Show

The Bluetooth Accessory iOS Would Not Show

I wanted a Linux box to receive an iPhone's notifications over ANCS, the Bluetooth LE service Apple built for smartwatches. The advertisement was exactly what the spec describes, btmon confirmed it was on the air, and the iPhone never listed it. Two changes made it appear: a private address and a keyboard costume. Then a pairing prompt, an 'Allow notifications?' question, a subscription that had to be made twice, and a classic Bluetooth key that quietly changed underneath a working headset.

2026-11-15 8 min read
Blog
The Sound Was Seconds Late, and Nothing Was Slow

The Sound Was Seconds Late, and Nothing Was Slow

A phone's audio, relayed through a Linux box into a stream, slowly fell seconds behind the picture. Every stage ran in real time. Every stat said zero backlog. The cause was two clocks 0.03% apart and a pipe nobody was measuring, and the fix was not a smaller buffer. How the clues pointed at it, the two wrong fixes first, and the rate matching that ended it.

2026-11-15 7 min read
Blog
Memory Corruption, All the Way Down to the Register

Memory Corruption, All the Way Down to the Register

A CPU does not know what your program meant. It has one register that holds the address of the next instruction, and memory corruption is the art of deciding what goes into it. This is the first-principles account, down to the stack frame, the heap chunk, the vtable pointer, and the instruction pointer: why memory corruption is possible at all, the four ways a program's model of memory diverges from the machine's, why corrupted data becomes controlled execution, and why every mitigation we have is one move in an arms race over a fixed board.

2026-11-15 11 min read
Blog
The Complete Web Attack-Surface Checklist, Built on Seven Boundaries

The Complete Web Attack-Surface Checklist, Built on Seven Boundaries

Security looks like a thousand unrelated bugs. It is not. Every vulnerability is one move: an attacker crossed a trust boundary that was supposed to hold. This is the full mental model, the seven boundaries, the two battlefields that decide which weapon works, and then the complete testing checklist that follows from it, recon through chaining, every category with what to test and what a hit looks like.

2026-11-14 11 min read
Blog
AI Gave Everyone a Red Team. It Did Not Give Anyone Judgment.

AI Gave Everyone a Red Team. It Did Not Give Anyone Judgment.

AI dropped the cost of a red team to roughly the price of the tokens, and the easy conclusion is that security skill is now a commodity. That conclusion is wrong. AI collapsed the cost of execution and left judgment untouched, so all of the value moved to the part it did not touch: knowing which thing to run, whether the result is true, and who signs that the system is safe to ship. This is a first-principles argument for building your competitiveness on what does not change. The mechanism underneath the tools, the abstraction that transfers to the problem no one has solved yet, and the human need for safety that no model makes go away.

2026-11-13 5 min read
Blog
Benchmarking an Agent Without Lying to Yourself

Benchmarking an Agent Without Lying to Yourself

Most agent benchmarks are not wrong on purpose. They are contaminated: the task set leaked into training, the fixtures moved between runs, the judge graded the producer's own claims, the good-looking samples got kept. The number comes out high and means nothing. Here are the six places a benchmark lies to you, the disciplines that each one needs, and a diagram and a worked example of a benchmark cheap enough to run and honest enough to act on.

2026-10-15 7 min read