<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>krack on Referently.com</title>
    <link>https://referently.com/tags/krack/</link>
    <description>Recent content in krack on Referently.com</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-us</language>
    <lastBuildDate>Sat, 18 Apr 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://referently.com/tags/krack/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>The KRACK Attack: What It Was, What It Taught Us, and Where WPA2 Stands Today</title>
      <link>https://referently.com/the-krack-attack-what-it-was-what-it-taught-us-and-where-wpa2-stands-today/</link>
      <pubDate>Sat, 18 Apr 2026 00:00:00 +0000</pubDate>
      
      <guid>https://referently.com/the-krack-attack-what-it-was-what-it-taught-us-and-where-wpa2-stands-today/</guid>
      <description>In October 2017, security researcher Mathy Vanhoef published a paper describing Key Reinstallation Attacks — KRACK — against the WPA2 four-way handshake. The disclosure triggered emergency patches across every major operating system, router firmware, and WiFi chipset vendor simultaneously. It was the most significant WiFi security event between WEP&amp;rsquo;s collapse in the early 2000s and WPA3&amp;rsquo;s introduction in 2018. Understanding what KRACK was, and what it actually threatened, clarifies both the state of WPA2 security today and how the WiFi security ecosystem responds to structural vulnerabilities.</description>
    </item>
    
  </channel>
</rss>
