<?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>TLS on SILO</title>
    <link>https://silo.pgsty.com/tags/tls/</link>
    <description>Recent content in TLS on SILO</description>
    <generator>Hugo</generator>
    <language>en</language>
    
    
    
      <lastBuildDate>Wed, 16 Sep 2026 18:29:21 +0800</lastBuildDate>
    
    
      <atom:link href="https://silo.pgsty.com/tags/tls/index.xml" rel="self" type="application/rss+xml" />
    
    <item>
        <title>Go 1.27 TLS Defaults and OIDC Discovery Failure Modes</title>
        <link>https://silo.pgsty.com/blog/design/go127-tls-oidc-discovery/</link>
        <pubDate>Wed, 16 Sep 2026 00:00:00 +0000</pubDate>
        
        <guid>https://silo.pgsty.com/blog/design/go127-tls-oidc-discovery/</guid>
        <description>What the Go 1.27 toolchain move changed at the TLS layer, how to diagnose an OIDC discovery failure by phase, and which health endpoint actually reports an offline identity provider. Written from the investigation of issue #154: mechanisms verified by synthetic experiments, with the customer-side root cause explicitly left unconfirmed.</description>
      </item>
    
  </channel>
</rss>
