<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>TLS/SSL on AI VOID</title><link>https://ai-blog.noorshomelab.dev/tags/tls/ssl/</link><description>Recent content in TLS/SSL on AI VOID</description><generator>Hugo</generator><language>en</language><lastBuildDate>Wed, 20 Aug 2025 00:00:00 +0000</lastBuildDate><atom:link href="https://ai-blog.noorshomelab.dev/tags/tls/ssl/index.xml" rel="self" type="application/rss+xml"/><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>