<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>IoT Security on Nalar</title>
    <link>https://nalar.dev/tags/iot-security/</link>
    <description>Recent content in IoT Security 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/iot-security/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>ESP32 MQTT over TLS: Transport Encryption and Broker Authentication Are Separate</title>
      <link>https://nalar.dev/esp32-mqtt-tls-transport-encryption-broker-authentication/</link>
      <pubDate>Sat, 19 Sep 2026 00:00:00 +0000</pubDate>
      <guid>https://nalar.dev/esp32-mqtt-tls-transport-encryption-broker-authentication/</guid>
      <description>&lt;p&gt;An ESP32 that moves an MQTT connection from port 1883 to 8883 crosses more than a port boundary. The TCP stream is now expected to carry MQTT inside TLS. Data in transit is protected only when the TLS client also validates the broker certificate. MQTT username/password authentication is separate: credentials identify the client to the broker, while certificate validation identifies the broker to the ESP32.&lt;/p&gt;&#xA;&lt;p&gt;Calling this &amp;ldquo;MQTT with HTTPS&amp;rdquo; mixes two application protocols. MQTT does not become HTTP when TLS is added. MQTT can run over plain TCP or over a TLS-protected TCP connection.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
