<story><title>&quot;Pwned Passwords&quot; V2 With Half a Billion Passwords</title><url>https://www.troyhunt.com/ive-just-launched-pwned-passwords-version-2/</url></story><parent_chain><item><author>groovecoder</author><text>do &lt;i&gt;not&lt;/i&gt; skip the section on &amp;quot;Cloudflare, Privacy and k-Anonymity&amp;quot; ... it is a great summary of an elegant privacy solution.&lt;p&gt;And check out Cloudflare&amp;#x27;s detail post too:&lt;p&gt;&lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;blog.cloudflare.com&amp;#x2F;validating-leaked-passwords-with-k-anonymity&amp;#x2F;&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;blog.cloudflare.com&amp;#x2F;validating-leaked-passwords-with...&lt;/a&gt;</text></item></parent_chain><comment><author>skykooler</author><text>Why does 0000 have the largest number of hashes? Does SHA-1 not distribute hash values evenly?</text></comment>
<story><title>&quot;Pwned Passwords&quot; V2 With Half a Billion Passwords</title><url>https://www.troyhunt.com/ive-just-launched-pwned-passwords-version-2/</url></story><parent_chain><item><author>groovecoder</author><text>do &lt;i&gt;not&lt;/i&gt; skip the section on &amp;quot;Cloudflare, Privacy and k-Anonymity&amp;quot; ... it is a great summary of an elegant privacy solution.&lt;p&gt;And check out Cloudflare&amp;#x27;s detail post too:&lt;p&gt;&lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;blog.cloudflare.com&amp;#x2F;validating-leaked-passwords-with-k-anonymity&amp;#x2F;&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;blog.cloudflare.com&amp;#x2F;validating-leaked-passwords-with...&lt;/a&gt;</text></item></parent_chain><comment><author>jkaptur</author><text>I&amp;#x27;m a bit confused - why not distribute a serialized Bloom filter representing these passwords? That would seem to enable a compact representation (low Azure bill) and client-side querying (maximally preserving privacy).</text></comment>