<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>TLS on Nalar</title>
    <link>https://nalar.dev/tags/tls/</link>
    <description>Recent content in TLS on Nalar</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Thu, 03 Sep 2026 00:00:00 +0700</lastBuildDate>
    <atom:link href="https://nalar.dev/tags/tls/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Verify TLS Server Identity Without Bypasses</title>
      <link>https://nalar.dev/verify-tls-server-identity-without-bypasses/</link>
      <pubDate>Thu, 03 Sep 2026 00:00:00 +0700</pubDate>
      <guid>https://nalar.dev/verify-tls-server-identity-without-bypasses/</guid>
      <description>&lt;p&gt;A client can establish an encrypted TLS connection and still connect to the wrong server if it does not verify the server&amp;rsquo;s identity correctly. Encryption protects traffic from observation and modification only within the connection that was established. The client must also decide whether the endpoint at the other end is the service it intended to reach.&lt;/p&gt;&#xA;&lt;p&gt;This matters for browsers, API clients, background workers, mobile applications, service-to-service calls, update clients, and any other software that relies on TLS. A tempting workaround such as &amp;ldquo;disable certificate verification because the internal certificate is inconvenient&amp;rdquo; can turn a configuration problem into an authentication failure.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
