<story><title>Modern Anti-Spam and E2E Crypto (2014)</title><url>https://moderncrypto.org/mail-archive/messaging/2014/000780.html</url></story><parent_chain></parent_chain><comment><author>mikaraento</author><text>Previous discussions &lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;news.ycombinator.com&amp;#x2F;item?id=8275970&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;news.ycombinator.com&amp;#x2F;item?id=8275970&lt;/a&gt; and &lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;news.ycombinator.com&amp;#x2F;item?id=12300953&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;news.ycombinator.com&amp;#x2F;item?id=12300953&lt;/a&gt;&lt;p&gt;(not because I want to dismiss conversation here - did want to read up on it myself)</text></comment>
<story><title>Modern Anti-Spam and E2E Crypto (2014)</title><url>https://moderncrypto.org/mail-archive/messaging/2014/000780.html</url></story><parent_chain></parent_chain><comment><author>bascule</author><text>I think this is an area where functional encryption could help:&lt;p&gt;&lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;en.wikipedia.org&amp;#x2F;wiki&amp;#x2F;Functional_encryption&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;en.wikipedia.org&amp;#x2F;wiki&amp;#x2F;Functional_encryption&lt;/a&gt;&lt;p&gt;This would allow a client to combine a server-provided function that calculates a spam score with their private key such that the resulting function calculates a spam score on encrypted email. The client could then hand that function back to the server so it can perform server-side spam detection.&lt;p&gt;There are a number of drawbacks, including performance and general questions about the security of such a system. That said, I think this is probably the biggest problem (from the OP):&lt;p&gt;&amp;quot;The third problem is that spam filters rely quite heavily on security through obscurity, because it works well. Though some features are well known (sending IP, links) there are many others, and those are secret. If calculation was pushed to the client then spammers could see exactly what they had to randomise and the cross-propagation of reputations wouldn&amp;#x27;t work as well.&amp;quot;&lt;p&gt;Using functional encryption to provide server-side spam detection would still require handing a spam scoring function to the client so they can apply that function to their private key and hand the server a result. This would expose the internals of the spam detection routine to all clients, including spammers.&lt;p&gt;A difficult tradeoff.</text></comment>