<?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 AI VOID</title><link>https://ai-blog.noorshomelab.dev/tags/tls/</link><description>Recent content in TLS on AI VOID</description><generator>Hugo</generator><language>en</language><lastBuildDate>Wed, 24 Dec 2025 00:00:00 +0000</lastBuildDate><atom:link href="https://ai-blog.noorshomelab.dev/tags/tls/index.xml" rel="self" type="application/rss+xml"/><item><title>How HTTPS Works: Deep Dive into Internals</title><link>https://ai-blog.noorshomelab.dev/how-it-works/how-https-works-internally/</link><pubDate>Wed, 24 Dec 2025 00:00:00 +0000</pubDate><guid>https://ai-blog.noorshomelab.dev/how-it-works/how-https-works-internally/</guid><description>&lt;h2 id="introduction"&gt;Introduction&lt;/h2&gt;
&lt;p&gt;In the digital realm, securing communication between users and web services is paramount. Hypertext Transfer Protocol Secure (HTTPS) stands as the bedrock of secure web browsing, safeguarding sensitive data exchanged daily across the internet. It&amp;rsquo;s the &amp;ldquo;S&amp;rdquo; that transforms the familiar HTTP into a robust, encrypted, and authenticated channel.&lt;/p&gt;
&lt;p&gt;Understanding the internal workings of HTTPS is not merely an academic exercise; it&amp;rsquo;s a critical skill for developers, system administrators, and anyone invested in building and maintaining secure online experiences. As cyber threats evolve, a deep comprehension of the underlying security mechanisms allows for better design choices, more effective troubleshooting, and a stronger defense against malicious actors.&lt;/p&gt;</description></item><item><title>Chapter 10: Securing WebSocket Communication</title><link>https://ai-blog.noorshomelab.dev/chat-guide/chapter-10-websocket-security/</link><pubDate>Wed, 20 Aug 2025 00:00:00 +0000</pubDate><guid>https://ai-blog.noorshomelab.dev/chat-guide/chapter-10-websocket-security/</guid><description>&lt;p&gt;So far, our chat application uses JWT for HTTP authentication and passes the token as a query parameter for WebSockets. While this identifies the user, the actual WebSocket data transfer is currently unencrypted (WS://). For production, all traffic, especially sensitive chat messages, &lt;strong&gt;must&lt;/strong&gt; be encrypted using WSS (WebSocket Secure), which relies on TLS/SSL certificates. This chapter focuses on enabling WSS and reinforcing WebSocket authentication.&lt;/p&gt;
&lt;h3 id="purpose-of-this-chapter"&gt;Purpose of this Chapter&lt;/h3&gt;
&lt;p&gt;By the end of this chapter, you will:&lt;/p&gt;</description></item></channel></rss>