<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Insights on Fenko Security</title>
    <link>https://fenko.nz/blog/</link>
    <description>Recent content in Insights on Fenko Security</description>
    <generator>Hugo</generator>
    <language>en-US</language>
    <lastBuildDate>Mon, 31 Aug 2026 00:00:00 +1200</lastBuildDate>
    <atom:link href="https://fenko.nz/blog/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Does a multi-model pipeline make AI-generated code more secure?</title>
      <link>https://fenko.nz/blog/multi-model-ai-code-security/</link>
      <pubDate>Mon, 31 Aug 2026 00:00:00 +1200</pubDate>
      <guid>https://fenko.nz/blog/multi-model-ai-code-security/</guid>
      <description>&lt;p&gt;Generating the same thing with several models and comparing the results is a real practice, and it&amp;rsquo;s well documented. Addy Osmani&amp;rsquo;s &lt;a href=&#34;https://addyosmani.com/blog/ai-coding-workflow/&#34;&#xA;&#xA;&#xA;&#xA;&#xA; target=&#34;_blank&#34;&#xA; &#xA;&#xA;&#xA;&gt;2026 workflow post&lt;/a&gt; suggests trying &amp;ldquo;two or more LLMs in parallel to cross-check how they might approach the same problem differently.&amp;rdquo; A widely shared DEV writeup calls it &lt;a href=&#34;https://dev.to/leena_malhotra/a-practical-pattern-for-comparing-ai-generated-code-before-it-reaches-production-31lp&#34;&#xA;&#xA;&#xA;&#xA;&#xA; target=&#34;_blank&#34;&#xA; &#xA;&#xA;&#xA;&gt;the Comparison Pattern&lt;/a&gt; and gets specific: &amp;ldquo;Run it through three different models simultaneously. I use Claude Opus 4.6, GPT-5.4, and Gemini 3.1 Pro side by side.&amp;rdquo; Cursor&amp;rsquo;s forum has &lt;a href=&#34;https://forum.cursor.com/t/how-to-compare-multiple-models-on-the-same-task-and-review-each-other-s-code-automatically/144604&#34;&#xA;&#xA;&#xA;&#xA;&#xA; target=&#34;_blank&#34;&#xA; &#xA;&#xA;&#xA;&gt;a standing request&lt;/a&gt; to automate the whole loop. There&amp;rsquo;s an academic version too: &lt;a href=&#34;https://arxiv.org/abs/2503.15838&#34;&#xA;&#xA;&#xA;&#xA;&#xA; target=&#34;_blank&#34;&#xA; &#xA;&#xA;&#xA;&gt;EnsLLM&lt;/a&gt; collects candidates from several LLMs and uses similarity scoring and a voting step to pick the one they agree on most, and it beats the best single model on HumanEval, 90.2% against 83.5%.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Fenko Vault: what it is, how it works, and what&#39;s left before 1.0</title>
      <link>https://fenko.nz/blog/fenko-vault-road-to-1-0/</link>
      <pubDate>Wed, 05 Aug 2026 00:00:00 +1200</pubDate>
      <guid>https://fenko.nz/blog/fenko-vault-road-to-1-0/</guid>
      <description>&lt;p&gt;&lt;a href=&#34;https://fenko.nz/fenko-vault/&#34;&#xA;&#xA;&#xA;&#xA;&#xA; target=&#34;_blank&#34;&#xA; &#xA;&#xA;&#xA;&gt;Fenko Vault&lt;/a&gt; is past 15,000 installs across Chrome, Firefox and Google Play, and the Chrome Web Store has picked up the listing as Featured. That is more people than we expected to be running a tool we originally wrote for ourselves, and a good moment to write down what it actually does, where it came from, and what still has to happen before the version number stops starting with a zero.&lt;/p&gt;</description>
    </item>
    <item>
      <title>One Colon to Rule Them All: HTTP Request Smuggling in Eclipse Grizzly</title>
      <link>https://fenko.nz/blog/grizzly-http-request-smuggling/</link>
      <pubDate>Tue, 28 Jul 2026 00:00:00 +1200</pubDate>
      <guid>https://fenko.nz/blog/grizzly-http-request-smuggling/</guid>
      <description>&lt;p&gt;Most request smuggling bugs are about disagreement. A front-end proxy reads a request one way, the backend reads it another, and the gap between those two readings is where you live. The interesting ones usually hinge on some baroque interaction between &lt;code&gt;Content-Length&lt;/code&gt; and &lt;code&gt;Transfer-Encoding&lt;/code&gt;, the kind of thing that takes three diagrams to explain.&lt;/p&gt;</description>
    </item>
    <item>
      <title>The rise of qualitative measurement</title>
      <link>https://fenko.nz/blog/the-rise-of-qualitative-measurement/</link>
      <pubDate>Sat, 27 Jun 2026 09:00:00 +1200</pubDate>
      <guid>https://fenko.nz/blog/the-rise-of-qualitative-measurement/</guid>
      <description>&lt;p&gt;I have a pet peeve that has followed me through every security job I&amp;rsquo;ve held, and it gets worse the more senior the room. We measure quality with numbers, and the numbers keep lying to us. Not because someone faked them. Because the thing we care about was never a number in the first place, and we pinned it to one anyway because we had no other option.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Tax the chips, before the models</title>
      <link>https://fenko.nz/blog/tax-the-chips-before-the-models/</link>
      <pubDate>Thu, 04 Jun 2026 00:00:00 +1200</pubDate>
      <guid>https://fenko.nz/blog/tax-the-chips-before-the-models/</guid>
      <description>&lt;p&gt;In 1930, with the world sliding into the Depression, John Maynard Keynes sat down and wrote something wildly optimistic. The essay was called &lt;em&gt;Economic Possibilities for our Grandchildren&lt;/em&gt;, and the bet at the center of it was simple: machines were getting good enough, fast enough, that within a hundred years the economic problem would basically be solved. His grandchildren, he figured, would work about fifteen hours a week. The rest of the time they&amp;rsquo;d spend on life. Art, friends, leisure, the stuff you actually remember.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Harness the Power of the Harness</title>
      <link>https://fenko.nz/blog/harness-the-power-of-the-harness/</link>
      <pubDate>Tue, 26 May 2026 00:00:00 +1200</pubDate>
      <guid>https://fenko.nz/blog/harness-the-power-of-the-harness/</guid>
      <description>&lt;p&gt;Microsoft topped a cybersecurity benchmark last week and the headlines all read &amp;ldquo;Microsoft beat Anthropic.&amp;rdquo; That&amp;rsquo;s the wrong story. Read the numbers again.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Hours, Not Days</title>
      <link>https://fenko.nz/blog/hours-not-days-patching-urgency/</link>
      <pubDate>Mon, 11 May 2026 00:00:00 +1200</pubDate>
      <guid>https://fenko.nz/blog/hours-not-days-patching-urgency/</guid>
      <description>&lt;p&gt;I&amp;rsquo;ve been banging on about mean time to exploit for a while. Recent events make it worth saying again.&lt;/p&gt;</description>
    </item>
    <item>
      <title>pip install malware: Why Python and JavaScript Package Ecosystems Are [almost] Unfixable</title>
      <link>https://fenko.nz/blog/pip-install-malware/</link>
      <pubDate>Thu, 09 Apr 2026 00:00:00 +1200</pubDate>
      <guid>https://fenko.nz/blog/pip-install-malware/</guid>
      <description>&lt;p&gt;pip, npm, and many other package managers are fundamentally broken from a security perspective. Not broken as in &amp;ldquo;needs patches.&amp;rdquo; Broken as in the core design makes the problem almost unsolvable.&lt;/p&gt;</description>
    </item>
    <item>
      <title>To Catch a Rising (AI) Star</title>
      <link>https://fenko.nz/blog/to-catch-a-rising-ai-star/</link>
      <pubDate>Thu, 03 Apr 2025 00:00:00 +1300</pubDate>
      <guid>https://fenko.nz/blog/to-catch-a-rising-ai-star/</guid>
      <description>&lt;p&gt;If your day-to-day life is primarily behind your monitor and keyboard, this article is for you. AI is coming fast for our jobs, and most of us are not as alarmed as we should be, nor know what to do about it. I&amp;rsquo;ve spent the last 12 months digging deeper and deeper into Generative AI, spent 100s of hours building tools with all the &amp;ldquo;standard&amp;rdquo; architectures, and I&amp;rsquo;ve come to some conclusions that I&amp;rsquo;d like to share with the rest of us. I&amp;rsquo;m hoping this gives you the point of view that I think we should all have.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
