<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic WPA3 - Another day, another flawed protocol... in Tech Talk</title>
    <link>https://community.isc2.org/t5/Tech-Talk/WPA3-Another-day-another-flawed-protocol/m-p/26396#M1639</link>
    <description>&lt;P&gt;The &lt;A href="https://wpa3.mathyvanhoef.com/" target="_blank" rel="noopener"&gt;Dragonblood team&lt;/A&gt; continue to hack away at WPA3. To their credit they have found that the initial recommendation to use Brainpool curves, was go figure, not a good one. It introduces another class of side-channel leaks in the Dragonfly handshake of WPA3.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;The new side-channel leak is located in the password encoding algorithm of Dragonfly. This algorithm first tries to find a hash output that is smaller than the prime of the elliptic curve being used. With the default NIST curves, such a hash output is practically always found immediately! However, with Brainpool curves, several iterations may have to be executed before finding a hash output smaller than the prime. What was found that only 8 iterations are needed! That costs less than $1 of EC2 compute time! Check out the research at this years Black Hat!&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Ps. don't get PWNED!&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Mon, 09 Oct 2023 09:17:39 GMT</pubDate>
    <dc:creator>AppDefects</dc:creator>
    <dc:date>2023-10-09T09:17:39Z</dc:date>
    <item>
      <title>WPA3 - Another day, another flawed protocol...</title>
      <link>https://community.isc2.org/t5/Tech-Talk/WPA3-Another-day-another-flawed-protocol/m-p/26396#M1639</link>
      <description>&lt;P&gt;The &lt;A href="https://wpa3.mathyvanhoef.com/" target="_blank" rel="noopener"&gt;Dragonblood team&lt;/A&gt; continue to hack away at WPA3. To their credit they have found that the initial recommendation to use Brainpool curves, was go figure, not a good one. It introduces another class of side-channel leaks in the Dragonfly handshake of WPA3.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;The new side-channel leak is located in the password encoding algorithm of Dragonfly. This algorithm first tries to find a hash output that is smaller than the prime of the elliptic curve being used. With the default NIST curves, such a hash output is practically always found immediately! However, with Brainpool curves, several iterations may have to be executed before finding a hash output smaller than the prime. What was found that only 8 iterations are needed! That costs less than $1 of EC2 compute time! Check out the research at this years Black Hat!&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Ps. don't get PWNED!&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 09 Oct 2023 09:17:39 GMT</pubDate>
      <guid>https://community.isc2.org/t5/Tech-Talk/WPA3-Another-day-another-flawed-protocol/m-p/26396#M1639</guid>
      <dc:creator>AppDefects</dc:creator>
      <dc:date>2023-10-09T09:17:39Z</dc:date>
    </item>
  </channel>
</rss>

