<?xml version="1.0" encoding="ISO-8859-1"?>
<rss version="2.0"
xmlns:dc="http://purl.org/dc/elements/1.1/"
xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
xmlns:admin="http://webns.net/mvcb/"
xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
xmlns:content="http://purl.org/rss/1.0/modules/content/"
xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
<title>StumbleUpon | Comments &amp;#38; Reviews of Did NSA Put a Secret Backdoor in New Encryption Standard? </title>
<link>http://www.stumbleupon.com/url/www.wired.com/politics/security/commentary/securitymatters/2007/11/securitymatters_1115</link>
<description>Comments &amp;#38; Reviews of http://www.wired.com/politics/security/commentary/securitymatters/2007/11/securitymatters_1115 on StumbleUpon</description>
<language>en-us</language>
<pubDate>Sat, 06 Sep 2008 16:57:08 -0700</pubDate>
<lastBuildDate>Sat, 09 Aug 2008 06:49:44 -0700</lastBuildDate>
<admin:generatorAgent rdf:resource="http://www.stumbleupon.com/" />
<atom:link href="http://rss.stumbleupon.com/url/www.wired.com/politics/security/commentary/securitymatters/2007/11/securitymatters_1115" rel="self" type="application/rss+xml" />
<image>
	<title>StumbleUpon | Comments &amp;#38; Reviews of Did NSA Put a Secret Backdoor in New Encryption Standard? </title>
	<link>http://www.stumbleupon.com/url/www.wired.com/politics/security/commentary/securitymatters/2007/11/securitymatters_1115</link>
	<url>http://cdn.stumble-upon.com/images/logo_su_36x36.png</url>
</image>
<item>
<pubDate>Sun, 13 Jan 2008 20:08:15 -0800</pubDate>
<link>http://shiitake.stumbleupon.com/review/16172882/</link>
<title>http://shiitake.stumbleupon.com/review/16172882/</title>
<enclosure url="http://cdn.stumble-upon.com/thumb/435/15213435.jpg" length="" type="image/jpeg" />
<description><![CDATA[<b>Shiitake</b> - From Bruce Schneier, noted expert on encryption.

Who has the keys to the backdoor in Microsoft Windows Vista?

From the page: "Of course, we have no way of knowing whether the NSA knows the secret numbers that break Dual_EC-DRBG [encryption]. We have no way of knowing whether an NSA employee working on his own came up with the constants -- and has the secret numbers. We don't know if someone from NIST, or someone in the ANSI working group, has them. Maybe nobody does.

We don't know where the constants came from in the first place. We only know that whoever came up with them could have the key to this backdoor. And we know there's no way for NIST -- or anyone else -- to prove otherwise."]]></description>
<comments>http://www.stumbleupon.com/url/www.wired.com/politics/security/commentary/securitymatters/2007/11/securitymatters_1115</comments>
</item>
<item>
<pubDate>Fri, 23 Nov 2007 21:52:43 -0800</pubDate>
<link>http://username2000.stumbleupon.com/review/14601829/</link>
<title>http://username2000.stumbleupon.com/review/14601829/</title>
<enclosure url="http://cdn.stumble-upon.com/thumb/435/15213435.jpg" length="" type="image/jpeg" />
<description><![CDATA[<b>Username2000</b> - From the page: "Random numbers are critical for cryptography: for encryption keys, random authentication challenges, initialization vectors, nonces, key-agreement schemes, generating prime numbers and so on. Break the random-number generator, and most of the time you break the entire security system. Which is why you should worry about a new random-number standard that includes an algorithm that is slow, badly designed and just might contain a backdoor for the National Security Agency."]]></description>
<comments>http://www.stumbleupon.com/url/www.wired.com/politics/security/commentary/securitymatters/2007/11/securitymatters_1115</comments>
</item>
<item>
<pubDate>Fri, 16 Nov 2007 03:00:46 -0800</pubDate>
<link>http://avangionq.stumbleupon.com/review/14371824/</link>
<title>http://avangionq.stumbleupon.com/review/14371824/</title>
<enclosure url="http://cdn.stumble-upon.com/thumb/435/15213435.jpg" length="" type="image/jpeg" />
<description><![CDATA[<b>AvangionQ</b> - If this is true and some hacker figures it out, the NSA is going to experience some blowback over it ... that said and on a more personal note, I like to keep speculation to a minimum and focus on what can be proven ...]]></description>
<comments>http://www.stumbleupon.com/url/www.wired.com/politics/security/commentary/securitymatters/2007/11/securitymatters_1115</comments>
</item>
<item>
<pubDate>Fri, 16 Nov 2007 02:32:14 -0800</pubDate>
<link>http://needsmorecoffee.stumbleupon.com/review/14371436/</link>
<title>http://needsmorecoffee.stumbleupon.com/review/14371436/</title>
<enclosure url="http://cdn.stumble-upon.com/thumb/435/15213435.jpg" length="" type="image/jpeg" />
<description><![CDATA[<b>NeedsMoreCoffee</b> - From the page: "What Shumow and Ferguson showed is that these numbers have a relationship with a second, secret set of numbers that can act as a kind of skeleton key. If you know the secret numbers, you can predict the output of the random-number generator after collecting just 32 bytes of its output. To put that in real terms, you only need to monitor one TLS internet encryption connection in order to crack the security of that protocol. If you know the secret numbers, you can completely break any instantiation of Dual_EC_DRBG.

The researchers don't know what the secret numbers are. But because of the way the algorithm works, the person who produced the constants might know; he had the mathematical opportunity to produce the constants and the secret numbers in tandem.

Of course, we have no way of knowing whether the NSA knows the secret numbers that break Dual_EC-DRBG. We have no way of knowing whether an NSA employee working on his own came up with the constants -- and has the secret numbers. We don't know if someone from NIST, or someone in the ANSI working group, has them. Maybe nobody does.

We don't know where the constants came from in the first place. We only know that whoever came up with them could have the key to this backdoor. And we know there's no way for NIST -- or anyone else -- to prove otherwise."]]></description>
<comments>http://www.stumbleupon.com/url/www.wired.com/politics/security/commentary/securitymatters/2007/11/securitymatters_1115</comments>
</item>
<item>
<pubDate>Thu, 15 Nov 2007 13:54:19 -0800</pubDate>
<link>http://barrelhead.stumbleupon.com/review/14355451/</link>
<title>http://barrelhead.stumbleupon.com/review/14355451/</title>
<enclosure url="http://cdn.stumble-upon.com/thumb/435/15213435.jpg" length="" type="image/jpeg" />
<description><![CDATA[<b>barrelhead</b> - Commentary by  Bruce Schneier]]></description>
<comments>http://www.stumbleupon.com/url/www.wired.com/politics/security/commentary/securitymatters/2007/11/securitymatters_1115</comments>
</item>
<item>
<pubDate>Thu, 15 Nov 2007 12:20:15 -0800</pubDate>
<link>http://leonz.stumbleupon.com/review/14352973/</link>
<title>http://leonz.stumbleupon.com/review/14352973/</title>
<enclosure url="http://cdn.stumble-upon.com/thumb/435/15213435.jpg" length="" type="image/jpeg" />
<description><![CDATA[<b>LeonZ</b> - Who would have expected something like that from NIST and NSA. Har...]]></description>
<comments>http://www.stumbleupon.com/url/www.wired.com/politics/security/commentary/securitymatters/2007/11/securitymatters_1115</comments>
</item>
<item>
<pubDate>Thu, 15 Nov 2007 10:54:57 -0800</pubDate>
<link>http://msaleem-stumbl.stumbleupon.com/review/14350866/</link>
<title>http://msaleem-stumbl.stumbleupon.com/review/14350866/</title>
<enclosure url="http://cdn.stumble-upon.com/thumb/435/15213435.jpg" length="" type="image/jpeg" />
<description><![CDATA[<b>msaleem-stumbl</b> - Random numbers are critical for cryptography: for encryption keys, random authentication challenges, initialization vectors, nonces, key-agreement schemes, generating prime numbers and so on. Break the random-number generator, and most of the time you break the entire security system. Which is why you should worry about a new random-number standard that includes an algorithm that is slow, badly designed and just might contain a backdoor for the National Security Agency.]]></description>
<comments>http://www.stumbleupon.com/url/www.wired.com/politics/security/commentary/securitymatters/2007/11/securitymatters_1115</comments>
</item>
<item>
<pubDate>Thu, 15 Nov 2007 05:54:50 -0800</pubDate>
<link>http://leonardodavinci.stumbleupon.com/review/14343898/</link>
<title>http://leonardodavinci.stumbleupon.com/review/14343898/</title>
<enclosure url="http://cdn.stumble-upon.com/thumb/435/15213435.jpg" length="" type="image/jpeg" />
<description><![CDATA[<b>LeonardoDaVinci</b> - So what's all the hoo-dee-dah about random numbers, other the obvious ones mentioned here? This: that there's really no such thing as a "truly" random number.]]></description>
<comments>http://www.stumbleupon.com/url/www.wired.com/politics/security/commentary/securitymatters/2007/11/securitymatters_1115</comments>
</item>
<item>
<pubDate>Thu, 15 Nov 2007 04:30:47 -0800</pubDate>
<link>http://moookid.stumbleupon.com/review/14342461/</link>
<title>http://moookid.stumbleupon.com/review/14342461/</title>
<enclosure url="http://cdn.stumble-upon.com/thumb/435/15213435.jpg" length="" type="image/jpeg" />
<description><![CDATA[<b>moookid</b> - From the page: "you only need to monitor one TLS internet encryption connection in order to crack the security of that protocol. If you know the secret numbers, you can completely break any instantiation of Dual_EC_DRBG.

The researchers don't know what the secret numbers are. But because of the way the algorithm works, the person who produced the constants might know; he had the mathematical opportunity to produce the constants and the secret numbers in tandem.

Of course, we have no way of knowing whether the NSA knows the secret numbers that break Dual_EC-DRBG. We have no way of knowing whether an NSA employee working on his own came up with the constants -- and has the secret numbers. We don't know if someone from NIST, or someone in the ANSI working group, has them. Maybe nobody does."]]></description>
<comments>http://www.stumbleupon.com/url/www.wired.com/politics/security/commentary/securitymatters/2007/11/securitymatters_1115</comments>
</item>
</channel>
</rss>
