<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Project on unrooted's blog</title><link>https://unrooted.github.io/tags/project/</link><description>Recent content in Project on unrooted's blog</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Sun, 07 Jun 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://unrooted.github.io/tags/project/index.xml" rel="self" type="application/rss+xml"/><item><title>RedSand - version 2.2</title><link>https://unrooted.github.io/posts/redsand-2.2/</link><pubDate>Sun, 07 Jun 2026 00:00:00 +0000</pubDate><guid>https://unrooted.github.io/posts/redsand-2.2/</guid><description>&lt;h2 id="what-is-redsand"&gt;What is RedSand?&lt;/h2&gt;
&lt;p&gt;RedSand started as a single &lt;code&gt;.wsb&lt;/code&gt; file: double-click it, get a clean Windows Sandbox for poking at malware or untrusted software, as it&amp;rsquo;s built on top of Windows Sandbox, that&amp;rsquo;d seem rational. That was useful, but most of the actual work — picking the right isolation knobs, pre-staging tools etc. — was left to you. Been a while since I&amp;rsquo;ve worked on it, but after recent moving my personal workflows over to macOS, I&amp;rsquo;ve decided to revisit this (hard to admit, but I sometimes miss Windows and it&amp;rsquo;s weirdness, so I keep it on my old ThinkPad), see which capabilities of Windows Sandbox have changed and whatnot. RedSand has grown into a small toolkit around that one idea: opinionated profiles for distinct workflows, helper scripts that do the boring parts, and CI that catches drift before users do.&lt;/p&gt;</description></item></channel></rss>