<?xml version="1.0" encoding="utf-8"?>
<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>Techdirt. Stories filed under &quot;gsm&quot;</title>
<description>Easily digestible tech news...</description>
<link>http://www.techdirt.com/</link>
<language>en-us</language>
<image><title>Techdirt. Stories filed under &quot;gsm&quot;</title><url>http://www.techdirt.com/images/td-88x31.gif</url><link>http://www.techdirt.com/</link></image>
<item>
<pubDate>Tue, 29 Dec 2009 15:15:00 PST</pubDate>
<title>GSM Encryption Cracked... GSMA's First Response?  That's Illegal!</title>
<dc:creator>Mike Masnick</dc:creator>
<link>http://www.techdirt.com/articles/20091229/1044447528.shtml</link>
<guid>http://www.techdirt.com/articles/20091229/1044447528.shtml</guid>
<description><![CDATA[ The big news in security circles this week is the fact that a security researcher claims to have <a href="http://news.bbc.co.uk/2/hi/technology/8429233.stm" target="_blank">cracked the encryption used to keep GSM mobile phone calls private</a>.  It looks like he and some collaborators used a brute force method.  He admits that it requires about $30,000 worth of equipment to de-crypt calls in real-time, but that's pocket change for many of the folks who would want to make use of this.  What's much more interesting (and worrisome) is the GSM Association's (GSMA) <a href="http://www.nytimes.com/2009/12/29/technology/29hack.html" target="_blank">response to this news</a>:
<blockquote><i>
"This is theoretically possible but practically unlikely," said Claire Cranton, an association spokeswoman. She said no one else had broken the code since its adoption. "What he is doing would be illegal in Britain and the United States. To do this while supposedly being concerned about privacy is beyond me."
</i></blockquote>
There are so many things wrong with that statement it's hard to know where to begin.  First, claiming it's "theoretically possible, but practically unlikely" means that it's very, very possible and quite likely.  To then say that no one else had broken the code since its adoption fifteen years ago is almost certainly false.  What she means is that no one <i>else</i> who's broken the code has <i>gone public</i> with it -- probably because it's much more lucrative keeping that info to themselves.  Next, blaming the messenger by announcing that cracking the code is "illegal in Britain and the United States" is not what anyone who uses a GSM phone should want to hear.  They should want to know how the GSMA is <i>responding</i> and fixing <i>the problem</i> -- not how they're responding to the <i>public release</i>.  Finally, if it's "beyond" her why cracking a code used for private conversations and showing that it's insecure is all about being concerned about "privacy" -- she should be looking for a different job.  This has everything to do with privacy.  The GSMA claims that the code is secure for private conversations, and this group of folks is showing that it is not.  That seems to have everything to do with privacy.<br /><br /><a href="http://www.techdirt.com/articles/20091229/1044447528.shtml">Permalink</a> | <a href="http://www.techdirt.com/articles/20091229/1044447528.shtml#comments">Comments</a> | <a href="http://www.techdirt.com/articles/20091229/1044447528.shtml?op=sharethis">Email This Story</a><br />
 ]]></description>
<slash:department>yeah,-because-the-eavesdroppers-care</slash:department>
<wfw:commentRss>http://www.techdirt.com/comment_rss.php?sid=20091229/1044447528</wfw:commentRss>
</item>
<item>
<pubDate>Thu, 6 Dec 2007 08:16:00 PST</pubDate>
<title>AT&#038;T Does Nothing, Convinces Reporter It Has Now 'Opened' Its Network</title>
<dc:creator>Mike Masnick</dc:creator>
<link>http://www.techdirt.com/articles/20071206/030232.shtml</link>
<guid>http://www.techdirt.com/articles/20071206/030232.shtml</guid>
<description><![CDATA[ When Verizon Wireless announced last month its plans to <a href="http://www.techdirt.com/articles/20071127/130723.shtml">"open" its network</a> some people noticed very quickly that what Verizon Wireless was announcing didn't sound any different from what <a href="http://mobhappy.com/blog1/2007/11/27/verizons-open-announcement-is-a-big-deal-but-not-for-the-reasons-you-might-think/">GSM operators, like AT&#038;T and T-Mobile already had</a>.  It was just that the GSM operators hadn't come up with the PR gimmick to call it "open."  Since they already had it though, it didn't take a genius to figure out that it wouldn't be long before they declared their networks open as well.  And, that appears to be exactly what AT&#038;T is doing -- but somehow, it appears that AT&#038;T's marketers have convinced a USA Today reporter that it's somehow changed its policies and is <a href="http://www.usatoday.com/tech/wireless/phones/2007-12-05-att_N.htm">"flinging" its network "wide open."</a>  The article starts off breathlessly announcing that "starting immediately" people can use any device on AT&#038;T's network.  Of course, the reason it's "starting immediately" is because, um, you've been able to do that ever since they launched their GSM network years ago.  Basically, absolutely nothing happened here except that AT&#038;T's marketing crew declared that AT&#038;T's network is now open, and convinced USA Today to report it as if it were a big deal.  If there was any change at all within AT&#038;T, it's that retail store employees are now supposed to admit that you can use other devices on the network, rather than pretending you can't.  Not quite as exciting as "flinging the network open," though.<br /><br /><a href="http://www.techdirt.com/articles/20071206/030232.shtml">Permalink</a> | <a href="http://www.techdirt.com/articles/20071206/030232.shtml#comments">Comments</a> | <a href="http://www.techdirt.com/articles/20071206/030232.shtml?op=sharethis">Email This Story</a><br />
 ]]></description>
<slash:department>nice-trick</slash:department>
<wfw:commentRss>http://www.techdirt.com/comment_rss.php?sid=20071206/030232</wfw:commentRss>
</item>
</channel>
</rss>