<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>하이브리드-TLS on gnosyslambda&#39;s log</title>
    <link>https://gnosyslambda.github.io/tags/%ED%95%98%EC%9D%B4%EB%B8%8C%EB%A6%AC%EB%93%9C-tls/</link>
    <description>Recent content in 하이브리드-TLS on gnosyslambda&#39;s log</description>
    <image>
      <title>gnosyslambda&#39;s log</title>
      <url>https://gnosyslambda.github.io/images/og-image.png</url>
      <link>https://gnosyslambda.github.io/images/og-image.png</link>
    </image>
    <generator>Hugo</generator>
    <language>ko-KR</language>
    <lastBuildDate>Sat, 04 Jul 2026 06:51:16 +0900</lastBuildDate>
    <atom:link href="https://gnosyslambda.github.io/tags/%ED%95%98%EC%9D%B4%EB%B8%8C%EB%A6%AC%EB%93%9C-tls/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>양자내성 TLS와 ML-KEM 표준화 쟁점</title>
      <link>https://gnosyslambda.github.io/posts/2026-07-04-post-quantum-tls-mlkem-standards/</link>
      <pubDate>Sat, 04 Jul 2026 06:51:16 +0900</pubDate>
      <guid>https://gnosyslambda.github.io/posts/2026-07-04-post-quantum-tls-mlkem-standards/</guid>
      <description>양자내성 TLS 전환에서 ML-KEM 단독 방식과 하이브리드 키 교환의 차이, 표준화 논쟁, 운영 리스크와 도입 조건을 정리합니다.</description>
    </item>
  </channel>
</rss>
