imabee

imabee

imabee is a systems engineer who builds the machinery other software assumes is there.

The job

The parts nobody notices until they stop.

Most software stands on something it never thinks about. A request goes out and an answer comes back, and nobody asks what happened in between.

What happens in between is my work: the handoff, the unexpected failure, and the way back.

HEADERS, then RST_STREAM, on every lane. Below: the work each one left running.

01 / Python

HTTP/2 Rapid Reset

A proof of concept for CVE-2023-44487, the HTTP/2 Rapid Reset denial-of-service flaw.

I wanted to watch the attack work rather than read about it. The proof of concept opens a stream, sends the headers, then resets it before the server can answer, and does that in a tight loop across thousands of connections. Reproducing it is the quickest way to understand how a protocol feature meant for efficiency became a cheap way to take a server down.

The whole flaw is an asymmetry in cost. Cancelling a stream is nearly free for the client, but the server has already dispatched the work behind it, and HTTP/2 multiplexing means the usual per-connection limits do not contain you. Writing the loop is easy. The uncomfortable part is seeing how little traffic it takes, and that the real fix lives in how servers account for reset streams, not in anything the client is doing wrong.

Source

stdin → process | process | process → stdout

02 / Rust

The shell on this site

A POSIX-style shell, compiled to WebAssembly and running in your browser.

The terminal on this site is the real thing, not a recording. It is a small POSIX-style shell with pipelines, redirection, globbing, a virtual filesystem and a few dozen coreutils, written in Rust and compiled to WebAssembly so every command you type runs locally in your browser with no server behind it.

Parsing a command line properly is more work than it looks. The parser is hand-written as a chain from lists, to and/or sequences, to pipelines, to single commands, each one splitting only at the top level so quotes and nested operators survive. Pipes hand stdout to the next stage as a plain string, which keeps the code small at the cost of being fully synchronous: a deliberate trade for fitting a believable shell into a page that still has to load fast.

Open it

One controller, a rack of machines, a line out to each.

03 / Go

conduit

A remote infrastructure management platform. API and frontend in one repository.

conduit manages fleets of remote machines from one place. It is a single Go binary that acts as both the control server and the agent you install on each host, with the web dashboard embedded straight into the executable. One file to deploy, agents that dial home, a browser session that can reach any of them.

The interesting problem is the middle. Browsers speak WebSocket; agents hold long-lived QUIC connections and fall back to WebSocket when a network will not pass UDP. Something has to sit between the two, route a session from a tab to the right machine and back, and survive reconnects and keepalives without trusting either end more than it should. Keeping that path up is most of the work. The dashboard is the easy part.

Source

Contact

Say something

A little curiosity. A lot of care.