<?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>SSE-C on SILO</title>
    <link>https://silo.pgsty.com/tags/sse-c/</link>
    <description>Recent content in SSE-C on SILO</description>
    <generator>Hugo</generator>
    <language>en</language>
    
    
    
      <lastBuildDate>Fri, 28 Aug 2026 18:47:42 +0800</lastBuildDate>
    
    
      <atom:link href="https://silo.pgsty.com/tags/sse-c/index.xml" rel="self" type="application/rss+xml" />
    
    <item>
        <title>Two SSE-C Keys, One CopyObject Response</title>
        <link>https://silo.pgsty.com/blog/design/copyobject-ssec-checksum-response/</link>
        <pubDate>Fri, 28 Aug 2026 00:00:00 +0000</pubDate>
        
        <guid>https://silo.pgsty.com/blog/design/copyobject-ssec-checksum-response/</guid>
        <description>CopyObject can carry one SSE-C key for the source and another for the destination. SILO stored the destination checksum correctly but tried to decrypt it for the response with the source key, silently omitting checksum fields. This record explains the key-context boundary, response-only repair, single-decryption design, and regression matrix.</description>
      </item>
    
  </channel>
</rss>
