<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>AMQP on SILO</title>
    <link>https://silo.pgsty.com/tags/amqp/</link>
    <description>Recent content in AMQP on SILO</description>
    <generator>Hugo</generator>
    <language>en</language>
    
    
    
      <lastBuildDate>Sat, 24 Oct 2026 18:19:49 +0800</lastBuildDate>
    
    
      <atom:link href="https://silo.pgsty.com/tags/amqp/index.xml" rel="self" type="application/rss+xml" />
    
    <item>
        <title>SN-2026-019: Notification Keyspace Registration and Validation Redaction</title>
        <link>https://silo.pgsty.com/blog/security/notify-keyspace-registration/</link>
        <pubDate>Tue, 04 Aug 2026 00:00:00 +0000</pubDate>
        
        <guid>https://silo.pgsty.com/blog/security/notify-keyspace-registration/</guid>
        <description>&lt;p&gt;&lt;strong&gt;&lt;code&gt;SN-2026-019&lt;/code&gt;&lt;/strong&gt; covers a class of notification configuration defects fixed in &lt;a href=&#34;https://github.com/pgsty/silo/releases/tag/RELEASE.2026-08-04T00-00-00Z&#34;&gt;Server 20260804&lt;/a&gt; (&lt;code&gt;162ded343&lt;/code&gt; and &lt;code&gt;672c07a0f&lt;/code&gt;, &lt;a href=&#34;https://github.com/pgsty/silo/issues/39&#34;&gt;&lt;code&gt;pgsty/silo#39&lt;/code&gt;&lt;/a&gt;): notification parser and legacy-migration paths read or wrote KVS configuration keys that were missing from &lt;code&gt;Default*KVS&lt;/code&gt;, while &lt;code&gt;CheckValidKeys&lt;/code&gt; echoed raw key values in validation errors and &lt;code&gt;FetchEnabledTargets&lt;/code&gt; aborted all active notification targets on the first validation failure. In &lt;a href=&#34;https://silo.pgsty.com/blog/design/notify-url/&#34;&gt;Server 20260903&lt;/a&gt; (&lt;code&gt;f1ba68358&lt;/code&gt;), the discrete PostgreSQL and MySQL host/credential keys uncovered by our AST audit were retired in favor of &lt;code&gt;connection_string&lt;/code&gt; and &lt;code&gt;dsn_string&lt;/code&gt;.&lt;/p&gt;</description>
      </item>
    
  </channel>
</rss>
