<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Powershell on Luther Monson</title>
    <link>https://luth.io/tags/powershell/</link>
    <description>Recent content in Powershell on Luther Monson</description>
    <generator>Hugo</generator>
    <language>en</language>
    <lastBuildDate>Tue, 29 Sep 2026 20:30:00 -0700</lastBuildDate>
    <atom:link href="https://luth.io/tags/powershell/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Your Agent&#39;s Shell Allowlist Is Bypassable</title>
      <link>https://luth.io/blog/2026/09/agent-shell-allowlist-bypassable/</link>
      <pubDate>Tue, 29 Sep 2026 20:30:00 -0700</pubDate>
      <guid>https://luth.io/blog/2026/09/agent-shell-allowlist-bypassable/</guid>
      <description>&lt;p&gt;Every &lt;a href=&#34;https://luth.io/blog/2026/08/shipmates-persona-based-ai-coding-crews/&#34;&gt;shipmates&lt;/a&gt; crew member runs shell commands. Before any of&#xA;them runs, it goes through a permission gate. The gate uses the same rule syntax as Claude Code settings:&#xA;&lt;code&gt;Bash(git status)&lt;/code&gt;, &lt;code&gt;Bash(rm *)&lt;/code&gt;, &lt;code&gt;Write(**/.claude/settings.json)&lt;/code&gt;. The rules are merged from several layers:&lt;/p&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;a fleet-wide deny list pushed from Fleet Command&lt;/li&gt;&#xA;&lt;li&gt;per-persona policy files&lt;/li&gt;&#xA;&lt;li&gt;project settings&lt;/li&gt;&#xA;&lt;li&gt;the Brig, which compiles shipmates&amp;rsquo; fifteen &amp;ldquo;Ship&amp;rsquo;s Articles&amp;rdquo; into deny and ask rules&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;p&gt;Deny beats ask, ask beats allow.&lt;/p&gt;</description>
    </item>
    <item>
      <title>A 1 TB Test: Building a Memory Watchdog for go test</title>
      <link>https://luth.io/blog/2026/09/memory-watchdog-for-go-test/</link>
      <pubDate>Tue, 22 Sep 2026 20:48:00 -0700</pubDate>
      <guid>https://luth.io/blog/2026/09/memory-watchdog-for-go-test/</guid>
      <description>&lt;p&gt;On August 16th a &lt;code&gt;server.test.exe&lt;/code&gt; from &lt;a href=&#34;https://luth.io/blog/2026/08/shipmates-persona-based-ai-coding-crews/&#34;&gt;shipmates&lt;/a&gt; climbed to&#xA;roughly &lt;strong&gt;1 TB of commit charge&lt;/strong&gt; on my Windows workstation. Windows Terminal was hosting several agent sessions in&#xA;tabs. It hard-faulted with &lt;code&gt;E_OUTOFMEMORY&lt;/code&gt;, and every one of those sessions died at the same moment. It wasn&amp;rsquo;t the&#xA;first time either. An earlier one hit about 236 GB through an infinite &lt;code&gt;filepath.Dir&lt;/code&gt; loop.&lt;/p&gt;&#xA;&lt;p&gt;The machine has 128 GB of RAM. Commit charge doesn&amp;rsquo;t care. It&amp;rsquo;s backed by the page file, and Windows will happily let&#xA;a process reserve-and-commit until the commit limit is gone. Then everything else on the desktop starts failing&#xA;allocations too.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
