<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Security on Barn</title>
    <link>https://barn.pgsty.com/tags/security/</link>
    <description>Recent content in Security on Barn</description>
    <generator>Hugo</generator>
    <language>en-US</language>
    
    
    
      <lastBuildDate>Wed, 11 Nov 2026 00:00:00 +0800</lastBuildDate>
    
    
      <atom:link href="https://barn.pgsty.com/tags/security/index.xml" rel="self" type="application/rss+xml" />
    
    <item>
        <title>Pigsty host setup: fixed names and CA trust</title>
        <link>https://barn.pgsty.com/blog/design/pigsty-host-setup/</link>
        <pubDate>Wed, 11 Nov 2026 00:00:00 +0800</pubDate>
        
        <guid>https://barn.pgsty.com/blog/design/pigsty-host-setup/</guid>
        <description>&lt;p&gt;&lt;strong&gt;Recommend one optional host setup operation: install a fixed set of Pigsty names and trust the lab&amp;rsquo;s public root CA certificate.&lt;/strong&gt; Keep one entry address, defaulting to &lt;code&gt;10.10.10.10&lt;/code&gt;, and reuse the same CA across ordinary lab rebuilds. With unchanged names, address and CA trust, setup is a no-op and needs no elevation. This gives the common lab a mostly one-time host integration step.&lt;/p&gt;&#xA;&lt;p&gt;&lt;strong&gt;Status — 2026-11-11: proposal, not implemented.&lt;/strong&gt; This narrows the first delivery from the earlier &lt;a href=&#34;https://barn.pgsty.com/blog/design/pigsty-host-dns/&#34;&gt;full host-DNS design&lt;/a&gt;. General inventory extraction, dynamic node/PG/VIP publication, split DNS and a resident DNS service remain optional future work. Their implementation is not a prerequisite for this fixed profile. This review changed documentation only; it did not read a CA private key, install trust, modify system hosts or operate VMs.&lt;/p&gt;</description>
      </item>
    
  </channel>
</rss>
