<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Hacker News: tr32q423</title><link>https://news.ycombinator.com/user?id=tr32q423</link><description>Hacker News RSS</description><docs>https://hnrss.org/</docs><generator>hnrss v2.1.1</generator><lastBuildDate>Fri, 01 May 2026 20:12:06 +0000</lastBuildDate><atom:link href="https://hnrss.org/user?id=tr32q423" rel="self" type="application/rss+xml"></atom:link><item><title><![CDATA[New comment by tr32q423 in "Cloudflare Reverse Proxies Are Dumping Uninitialized Memory"]]></title><description><![CDATA[
<p>The root cause is apparently coming from auto-generated code that causes buffer overrun:<p><pre><code>    /* generated code */
    if ( ++p == pe )
        goto _test_eof;

</code></pre>
<i>With the help of Google, Yahoo, Bing and others, we found 770 unique URIs that had been cached and which contained leaked memory. Those 770 unique URIs covered 161 unique domains. </i><p>The examples in the report shows Uber, okcupid , etc. It would be good to know the full list, to know what password might have been compromised.<p><a href="https://blog.cloudflare.com/incident-report-on-memory-leak-caused-by-cloudflare-parser-bug/" rel="nofollow">https://blog.cloudflare.com/incident-report-on-memory-leak-c...</a></p>
]]></description><pubDate>Fri, 24 Feb 2017 00:34:01 +0000</pubDate><link>https://news.ycombinator.com/item?id=13719530</link><dc:creator>tr32q423</dc:creator><comments>https://news.ycombinator.com/item?id=13719530</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=13719530</guid></item></channel></rss>