<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>prompt-injection on HBCC</title><link>https://www.handsomeboyscomputer.club/tags/prompt-injection/</link><description>Recent content in prompt-injection on HBCC</description><generator>Hugo</generator><language>en</language><lastBuildDate>Tue, 03 Nov 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://www.handsomeboyscomputer.club/tags/prompt-injection/index.xml" rel="self" type="application/rss+xml"/><item><title>A CVE triage pipeline that keeps asking, because day one tells you nothing</title><link>https://www.handsomeboyscomputer.club/log/rappaport/</link><pubDate>Sat, 31 Oct 2026 00:00:00 +0000</pubDate><guid>https://www.handsomeboyscomputer.club/log/rappaport/</guid><description>&lt;p&gt;The pipeline is called Rappaport, after a scientist in Lem&amp;rsquo;s &lt;a href="https://en.wikipedia.org/wiki/His_Master%27s_Voice_%28novel%29"&gt;&lt;em&gt;His Master&amp;rsquo;s Voice&lt;/em&gt;&lt;/a&gt;, a novel in which a team of researchers reads meaning into a signal from the stars and slowly learns that the meaning tells them more about themselves than about the signal. That is the failure I kept meeting in the field. A detection stack returns a confident verdict, and the confidence comes from how little it has seen. When partial signal can corrupt the verdict, priority cannot be read off whatever a record claims about its own severity. It has to be computed from signal that actually predicts exploitation, before anything a model could be talked into gets near it.&lt;/p&gt;</description></item></channel></rss>