Charlie Warzel interviews Ondřej Surý about the work between an emergency PHP source release and a patch people can actually install. Surý prepares software packages, letting administrators update fleets of servers without compiling the language themselves. That work is a volunteer responsibility alongside his job at the nonprofit Internet Systems Consortium.

This is the maintenance story behind the PHP2Shell emergency patches. The existing incident page covers exposure, attack evidence and operational guidance.

A fix needs a delivery system

Surý says a leak compressed the release schedule from Thursday to Wednesday. Advance access let him prepare packages before public release. More than twenty years of experience and extensive automation made the accelerated rollout manageable.

He also pushes back on the lone-savior framing. The PHP project produced the fixes. Without his packages, administrators could use other sources or compile PHP themselves, though that would take more time and expertise. His contribution makes deployment easier and faster across many machines.

That distinction matters when attacks accelerate. Finding a flaw and writing a fix are only parts of the response. Someone has to build, distribute and install the corrected software.

Gratitude is a fragile funding model

Surý tells Warzel that donations arriving over one day roughly matched a year’s usual contributions. He also describes contingency discussions with Raphaël Hertzog at Freexian, whose expertise could support a handover if necessary. Those are discussions about continuity, not a completed succession arrangement.

His criticism is direct: “Open-source sometimes feels like exploitation.” He wants the organizations benefiting most from the work to compensate the people doing it. Thank-you messages give the work meaning, but appreciation alone leaves essential infrastructure dependent on volunteers’ availability.

Keep the incident claims separate

The interview’s roughly 70-percent PHP usage figure describes the language’s reach, not the number of exploitable websites. Surý also rejects the claim that older versions leave a third of the internet permanently unfixable.

PHP’s own guidance confirms fixed releases 8.2.35, 8.3.36, 8.4.27 and 8.5.12, plus vendor backports and limited source-backports for some older branches. Operators still need to confirm their running web workers use corrected code.

Caveat: the interview repeats reports of attack attempts; those counts do not establish successful compromises or uniform exposure across PHP installations.

Surý’s account brings the problem back to staffing and responsibility. Faster discovery increases the pressure on a delivery chain whose maintenance was already taken for granted.