<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Signal Protocol on Nalar</title>
    <link>https://nalar.dev/tags/signal-protocol/</link>
    <description>Recent content in Signal Protocol on Nalar</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Sat, 19 Sep 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://nalar.dev/tags/signal-protocol/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Signal Protocol Is a Cryptographic Layer, Not a Transport Protocol</title>
      <link>https://nalar.dev/signal-protocol-is-a-cryptographic-layer-not-a-transport-protocol/</link>
      <pubDate>Sat, 19 Sep 2026 00:00:00 +0000</pubDate>
      <guid>https://nalar.dev/signal-protocol-is-a-cryptographic-layer-not-a-transport-protocol/</guid>
      <description>&lt;h1 id=&#34;signal-protocol-is-a-cryptographic-layer-not-a-transport-protocol&#34;&gt;Signal Protocol Is a Cryptographic Layer, Not a Transport Protocol&lt;/h1&gt;&#xA;&lt;p&gt;A Go service can deliver messages over WebSocket, HTTP, WebRTC, MQTT, or a store-and-forward queue without any of those transports providing end-to-end encryption. Transport encryption such as TLS protects a connection between network peers. Signal Protocol addresses a different boundary: message content is encrypted at one endpoint and remains ciphertext until the receiving endpoint processes the corresponding cryptographic session.&lt;/p&gt;&#xA;&lt;p&gt;That distinction determines where Signal Protocol belongs in an application. The relay can authenticate accounts, route envelopes, retain undelivered ciphertext, and enforce quotas, but it should not need the conversation keys required to recover message plaintext.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
