<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Network-Security on ShieldedBytes</title>
    <link>https://linuxeries.org/tags/network-security/</link>
    <description>Recent content in Network-Security on ShieldedBytes</description>
    <generator>Hugo</generator>
    <language>en</language>
    <lastBuildDate>Wed, 04 Nov 2026 08:21:34 +0200</lastBuildDate>
    <atom:link href="https://linuxeries.org/tags/network-security/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>When Your Home Wi‑Fi Shows Up as “Unsecured” in GNOME but You’re on WPA2—Why the Mismatch Happens and How to Fix It</title>
      <link>https://linuxeries.org/post/2026-11-04-when-your-home-wifi-shows-up-as-unsecured-in-/</link>
      <pubDate>Wed, 04 Nov 2026 08:21:34 +0200</pubDate>
      <guid>https://linuxeries.org/post/2026-11-04-when-your-home-wifi-shows-up-as-unsecured-in-/</guid>
      <description>&lt;p&gt;GNOME’s network manager is great for quick connections, but it can throw you a curveball when it labels a WPA2‑PSK network as &lt;em&gt;Unsecured&lt;/em&gt;. The label isn’t a verdict on your router; it’s a symptom of how the client reads the wireless beacon. For anyone who takes Wi‑Fi security seriously, that mismatch is a red flag that needs a deeper look. Below is a practical walk‑through of why this happens, what it really means for your home network, and how to get rid of the false “Unsecured” label without touching your WPA2‑PSK setup.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
