<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://mises.org/Community/utility/FeedStylesheets/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>Crypto-Autonomist : security</title><link>http://mises.org/Community/blogs/crypto/archive/tags/security/default.aspx</link><description>Tags: security</description><dc:language>en</dc:language><generator>CommunityServer 2008.5 SP2 (Build: 40407.4157)</generator><item><title>Did the NSA put a backdoor in a new encryption standard?</title><link>http://mises.org/Community/blogs/crypto/archive/2007/11/15/did-the-nsa-put-a-backdoor-in-a-new-encryption-standard.aspx</link><pubDate>Fri, 16 Nov 2007 00:04:00 GMT</pubDate><guid isPermaLink="false">944abf2b-d1be-4bf2-990d-438cb0e377e9:3561</guid><dc:creator>Autonomist0</dc:creator><slash:comments>18</slash:comments><wfw:commentRss xmlns:wfw="http://wellformedweb.org/CommentAPI/">http://mises.org/Community/blogs/crypto/rsscomments.aspx?PostID=3561</wfw:commentRss><wfw:comment xmlns:wfw="http://wellformedweb.org/CommentAPI/">http://mises.org/Community/blogs/crypto/commentapi.aspx?PostID=3561</wfw:comment><comments>http://mises.org/Community/blogs/crypto/archive/2007/11/15/did-the-nsa-put-a-backdoor-in-a-new-encryption-standard.aspx#comments</comments><description>Because the government is a major consumer of crypto
products, government entities create or approve most of the encryption
standards used in the industry.&amp;nbsp; One of
the key ingredients of crypto technology are random number generators.&amp;nbsp; Getting random numbers from a computer is a
very tricky problem, so the U.S.
government actually publishes random number algorithms created by computer
scientists and government agencies.&amp;nbsp; This
year, the government produced a new standard, which may soon be integrated into
crypto software worldwide.&amp;nbsp; Three of the
four algorithms in the standard are based on industry standards, but one comes
from the National Security Agency.&amp;nbsp; The
NSA&amp;#39;s algorithm is more complex and slower than the others, so many people
wondered why the NSA pushed to have it included.&amp;nbsp; 



&lt;p&gt;In a recent CRYPTO 2007 conference, some &lt;a href="http://www.wired.com/politics/security/commentary/securitymatters/2007/11/securitymatters_1115"&gt;computer scientists
discovered that the algorithm has a possible backdoor key&lt;/a&gt;, which allows the
numbers it generates to be predicted.&amp;nbsp;
While we don&amp;#39;t know whether the NSA has the key, we can be sure that either
it has the key or it released a dangerously broken standard.&amp;nbsp; (Now that the vulnerability is known, vendors
are unlikely to use it, so the NSA wouldn&amp;#39;t have knowingly released a faulty
standard unless it had the key.)&lt;/p&gt;

&lt;p&gt;A paranoid person might wonder if having &lt;a href="http://en.wikipedia.org/wiki/Clipper_chip"&gt;failed &lt;/a&gt;to force broken
crypto on us at the hardware level, the government has some kind of nefarious
plan to sneak one in.&amp;nbsp; Simply requiring
that the standard be used by government contractors might be sufficient to get
it adopted by the industry due to its market share.&amp;nbsp; People take much more care in selecting and
testing encryption algorithms than random number generators.&lt;/p&gt;Reassuring answers on this issue are not likely to be forthcoming,
so here are some rules of thumb:



&lt;ul&gt;&lt;li&gt;Real security requires evaluating the whole process, not
just a good encryption algorithm.&lt;/li&gt;&lt;li&gt;Don&amp;#39;t trust a security solution just because it is widely used or
government approved.&lt;/li&gt;&lt;li&gt;Don&amp;#39;t trust a security solution that is isn&amp;#39;t open to peer
review.&lt;/li&gt;&lt;/ul&gt;







&lt;p&gt;&amp;nbsp;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://mises.org/Community/aggbug.aspx?PostID=3561" width="1" height="1"&gt;</description><category domain="http://mises.org/Community/blogs/crypto/archive/tags/cryptography/default.aspx">cryptography</category><category domain="http://mises.org/Community/blogs/crypto/archive/tags/security/default.aspx">security</category></item></channel></rss>