<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Sandboxing on VPN Works</title>
    <link>https://vpnw.com/tags/sandboxing/</link>
    <description>Recent content in Sandboxing on VPN Works</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Tue, 29 Sep 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://vpnw.com/tags/sandboxing/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Sealed Sandbox Case Study: A Script That Ignores Proxy Settings Tries Three Ways Out and Finds None</title>
      <link>https://vpnw.com/sealed-sandbox-case-study-a-script-that-ignores-proxy-settings-tries-three-ways-out-and-finds-none/</link>
      <pubDate>Tue, 29 Sep 2026 00:00:00 +0000</pubDate>
      <guid>https://vpnw.com/sealed-sandbox-case-study-a-script-that-ignores-proxy-settings-tries-three-ways-out-and-finds-none/</guid>
      <description>&lt;p&gt;A proxy setting is only a request. Most programs honor &lt;code&gt;HTTPS_PROXY&lt;/code&gt;, and a policy enforced at the proxy works for them. A program that has been told to leak something has every reason not to honor it. It can switch the proxy off, connect to an address directly or find a local service that will connect for it. A policy that only lives in the proxy never hears about any of that.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
