<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: How secure are your mobile calls?</title>
	<atom:link href="http://www.mobileindustryreview.com/2009/07/how_secure_are_your_mobile_calls.html/feed" rel="self" type="application/rss+xml" />
	<link>http://www.mobileindustryreview.com/2009/07/how_secure_are_your_mobile_calls.html</link>
	<description>Daily news and opinion for 250,000 industry executives and mobile fanatics</description>
	<lastBuildDate>Wed, 15 Feb 2012 10:31:00 +0100</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Rodolfo Rosini</title>
		<link>http://www.mobileindustryreview.com/2009/07/how_secure_are_your_mobile_calls.html/comment-page-1#comment-240796</link>
		<dc:creator>Rodolfo Rosini</dc:creator>
		<pubDate>Mon, 03 Aug 2009 23:16:04 +0000</pubDate>
		<guid isPermaLink="false">http://www.mobileindustryreview.com/?p=16519#comment-240796</guid>
		<description>Hi,&lt;br&gt;&lt;br&gt;just a quick disclaimer: I&#039;m the co-founder of Cellcrypt.&lt;br&gt;&lt;br&gt;Having said that you&#039;re 100% right on the soundproof room. I have spoken with customers that they have the same setup for their board meetings or emergency rooms. Pretty much they are protected to everything that requires proximity (lip reading, laser microphones etc) or physical access (bugging)&lt;br&gt;&lt;br&gt;What we do address is that you are constrained to that room and that is not always an option. Suppose your board meets once every month to discuss sensitive issues - how are your board members going to communicate the other 29 days? What if it&#039;s not a billion dollar deal but just millions. What if it&#039;s an emergency and you do not havethe luxury of time? The marginal cost (time and money) of the clean room or even having all team members flying in might be a factor in your decision to switch to encrypted calls.&lt;br&gt;&lt;br&gt;Imagine a scenario where you have people deployed in a developing country handling reconstruction projects. Maybe in a deserted area where it&#039;s pretty hard to have a secure room. Would you trust the network? You bet I would not.&lt;br&gt;&lt;br&gt;More to that point we have seen board members of large companies equipped with military handsets specifically for the reasons I just mentioned. And their usability is atrocious.&lt;br&gt;&lt;br&gt;On your second issue re handsets security you are also spot on. We need to be able to trust the device not just have secure communications. Only manufacturers can address this issue and they currently do it by locking down the devices and signing software but it&#039;s not a silver bullet.&lt;br&gt;I still prefer Cellcrypt to military handsets with 10 year old firmware (which is anyway a civilian solution stripped down of certain functionalities).&lt;br&gt;&lt;br&gt;My 0.02</description>
		<content:encoded><![CDATA[<p>Hi,</p>
<p>just a quick disclaimer: I&#39;m the co-founder of Cellcrypt.</p>
<p>Having said that you&#39;re 100% right on the soundproof room. I have spoken with customers that they have the same setup for their board meetings or emergency rooms. Pretty much they are protected to everything that requires proximity (lip reading, laser microphones etc) or physical access (bugging)</p>
<p>What we do address is that you are constrained to that room and that is not always an option. Suppose your board meets once every month to discuss sensitive issues &#8211; how are your board members going to communicate the other 29 days? What if it&#39;s not a billion dollar deal but just millions. What if it&#39;s an emergency and you do not havethe luxury of time? The marginal cost (time and money) of the clean room or even having all team members flying in might be a factor in your decision to switch to encrypted calls.</p>
<p>Imagine a scenario where you have people deployed in a developing country handling reconstruction projects. Maybe in a deserted area where it&#39;s pretty hard to have a secure room. Would you trust the network? You bet I would not.</p>
<p>More to that point we have seen board members of large companies equipped with military handsets specifically for the reasons I just mentioned. And their usability is atrocious.</p>
<p>On your second issue re handsets security you are also spot on. We need to be able to trust the device not just have secure communications. Only manufacturers can address this issue and they currently do it by locking down the devices and signing software but it&#39;s not a silver bullet.<br />I still prefer Cellcrypt to military handsets with 10 year old firmware (which is anyway a civilian solution stripped down of certain functionalities).</p>
<p>My 0.02</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: patrickjpr</title>
		<link>http://www.mobileindustryreview.com/2009/07/how_secure_are_your_mobile_calls.html/comment-page-1#comment-240790</link>
		<dc:creator>patrickjpr</dc:creator>
		<pubDate>Mon, 03 Aug 2009 19:33:23 +0000</pubDate>
		<guid isPermaLink="false">http://www.mobileindustryreview.com/?p=16519#comment-240790</guid>
		<description>&lt;span class=&quot;topsy_trackback_comment&quot;&gt;&lt;span class=&quot;topsy_twitter_username&quot;&gt;&lt;span class=&quot;topsy_trackback_content&quot;&gt;[client pimping] RT &lt;a href=&quot;http://topsy.com/twitter/rodolfor&quot;&gt;@rodolfor&lt;/a&gt;: Cellcrypt &quot;Not just a bit more secure but SHIT HOT secure&quot; woah http://ow.ly/iVK8&lt;/span&gt;
&lt;div class=&quot;topsy_trackback_links&quot;&gt;[&lt;a href=&quot;http://twitter.com/patrickjpr/status/3109854233&quot;&gt;Original tweet&lt;/a&gt;, &lt;a href=&quot;http://topsy.com/tb/www.mobileindustryreview.com/2009/07/how_secure_are_your_mobile_calls.html&quot;&gt;Topsy page&lt;/a&gt;]&lt;/div&gt;&lt;/span&gt;</description>
		<content:encoded><![CDATA[<p><span class="topsy_trackback_comment"><span class="topsy_twitter_username"><span class="topsy_trackback_content">[client pimping] RT <a href="http://topsy.com/twitter/rodolfor">@rodolfor</a>: Cellcrypt &#8220;Not just a bit more secure but SHIT HOT secure&#8221; woah <a href="http://ow.ly/iVK8" rel="nofollow">http://ow.ly/iVK8</a></span></p>
<div class="topsy_trackback_links">[<a href="http://twitter.com/patrickjpr/status/3109854233">Original tweet</a>, <a href="http://topsy.com/tb/www.mobileindustryreview.com/2009/07/how_secure_are_your_mobile_calls.html">Topsy page</a>]</div>
<p></span></span></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: patrickjpr</title>
		<link>http://www.mobileindustryreview.com/2009/07/how_secure_are_your_mobile_calls.html/comment-page-1#comment-240791</link>
		<dc:creator>patrickjpr</dc:creator>
		<pubDate>Mon, 03 Aug 2009 19:33:23 +0000</pubDate>
		<guid isPermaLink="false">http://www.mobileindustryreview.com/?p=16519#comment-240791</guid>
		<description>&lt;span class=&quot;topsy_trackback_comment&quot;&gt;&lt;span class=&quot;topsy_twitter_username&quot;&gt;&lt;span class=&quot;topsy_trackback_content&quot;&gt;[client pimping] RT &lt;a href=&quot;http://topsy.com/twitter/rodolfor&quot;&gt;@rodolfor&lt;/a&gt;: Cellcrypt &quot;Not just a bit more secure but SHIT HOT secure&quot; woah http://ow.ly/iVK8&lt;/span&gt;
&lt;div class=&quot;topsy_trackback_links&quot;&gt;[&lt;a href=&quot;http://twitter.com/patrickjpr/status/3109854233&quot;&gt;Original tweet&lt;/a&gt;, &lt;a href=&quot;http://topsy.com/tb/www.mobileindustryreview.com/2009/07/how_secure_are_your_mobile_calls.html&quot;&gt;Topsy page&lt;/a&gt;]&lt;/div&gt;&lt;/span&gt;</description>
		<content:encoded><![CDATA[<p><span class="topsy_trackback_comment"><span class="topsy_twitter_username"><span class="topsy_trackback_content">[client pimping] RT <a href="http://topsy.com/twitter/rodolfor">@rodolfor</a>: Cellcrypt &quot;Not just a bit more secure but SHIT HOT secure&quot; woah <a href="http://ow.ly/iVK8" rel="nofollow">http://ow.ly/iVK8</a></span></p>
<div class="topsy_trackback_links">[<a href="http://twitter.com/patrickjpr/status/3109854233">Original tweet</a>, <a href="http://topsy.com/tb/www.mobileindustryreview.com/2009/07/how_secure_are_your_mobile_calls.html">Topsy page</a>]</div>
<p></span></span></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Rodolfo</title>
		<link>http://www.mobileindustryreview.com/2009/07/how_secure_are_your_mobile_calls.html/comment-page-1#comment-240792</link>
		<dc:creator>Rodolfo</dc:creator>
		<pubDate>Mon, 03 Aug 2009 17:20:57 +0000</pubDate>
		<guid isPermaLink="false">http://www.mobileindustryreview.com/?p=16519#comment-240792</guid>
		<description>&lt;span class=&quot;topsy_trackback_comment&quot;&gt;&lt;span class=&quot;topsy_twitter_username&quot;&gt;&lt;span class=&quot;topsy_trackback_content&quot;&gt;Cellcrypt &quot;Not just a bit more secure but SHIT HOT secure&quot; woah http://ow.ly/iVK8&lt;/span&gt;
&lt;div class=&quot;topsy_trackback_links&quot;&gt;[&lt;a href=&quot;http://twitter.com/rodolfor/status/3107645851&quot;&gt;Original tweet&lt;/a&gt;, &lt;a href=&quot;http://topsy.com/tb/www.mobileindustryreview.com/2009/07/how_secure_are_your_mobile_calls.html&quot;&gt;Topsy page&lt;/a&gt;]&lt;/div&gt;&lt;/span&gt;</description>
		<content:encoded><![CDATA[<p><span class="topsy_trackback_comment"><span class="topsy_twitter_username"><span class="topsy_trackback_content">Cellcrypt &#8220;Not just a bit more secure but SHIT HOT secure&#8221; woah <a href="http://ow.ly/iVK8" rel="nofollow">http://ow.ly/iVK8</a></span></p>
<div class="topsy_trackback_links">[<a href="http://twitter.com/rodolfor/status/3107645851">Original tweet</a>, <a href="http://topsy.com/tb/www.mobileindustryreview.com/2009/07/how_secure_are_your_mobile_calls.html">Topsy page</a>]</div>
<p></span></span></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Cellcrypt</title>
		<link>http://www.mobileindustryreview.com/2009/07/how_secure_are_your_mobile_calls.html/comment-page-1#comment-240793</link>
		<dc:creator>Cellcrypt</dc:creator>
		<pubDate>Mon, 03 Aug 2009 17:19:33 +0000</pubDate>
		<guid isPermaLink="false">http://www.mobileindustryreview.com/?p=16519#comment-240793</guid>
		<description>&lt;span class=&quot;topsy_trackback_comment&quot;&gt;&lt;span class=&quot;topsy_twitter_username&quot;&gt;&lt;span class=&quot;topsy_trackback_content&quot;&gt;Mobile Industry Review: How secure are your mobile calls?
 http://ow.ly/iVK8&lt;/span&gt;
&lt;div class=&quot;topsy_trackback_links&quot;&gt;[&lt;a href=&quot;http://twitter.com/cellcrypt/status/3107622403&quot;&gt;Original tweet&lt;/a&gt;, &lt;a href=&quot;http://topsy.com/tb/www.mobileindustryreview.com/2009/07/how_secure_are_your_mobile_calls.html&quot;&gt;Topsy page&lt;/a&gt;]&lt;/div&gt;&lt;/span&gt;</description>
		<content:encoded><![CDATA[<p><span class="topsy_trackback_comment"><span class="topsy_twitter_username"><span class="topsy_trackback_content">Mobile Industry Review: How secure are your mobile calls?<br />
 <a href="http://ow.ly/iVK8" rel="nofollow">http://ow.ly/iVK8</a></span></p>
<div class="topsy_trackback_links">[<a href="http://twitter.com/cellcrypt/status/3107622403">Original tweet</a>, <a href="http://topsy.com/tb/www.mobileindustryreview.com/2009/07/how_secure_are_your_mobile_calls.html">Topsy page</a>]</div>
<p></span></span></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: rodolforosini</title>
		<link>http://www.mobileindustryreview.com/2009/07/how_secure_are_your_mobile_calls.html/comment-page-1#comment-239093</link>
		<dc:creator>rodolforosini</dc:creator>
		<pubDate>Mon, 03 Aug 2009 17:16:04 +0000</pubDate>
		<guid isPermaLink="false">http://www.mobileindustryreview.com/?p=16519#comment-239093</guid>
		<description>Hi,&lt;br&gt;&lt;br&gt;just a quick disclaimer: I&#039;m the co-founder of Cellcrypt.&lt;br&gt;&lt;br&gt;Having said that you&#039;re 100% right on the soundproof room. I have spoken with customers that they have the same setup for their board meetings or emergency rooms. Pretty much they are protected to everything that requires proximity (lip reading, laser microphones etc) or physical access (bugging)&lt;br&gt;&lt;br&gt;What we do address is that you are constrained to that room and that is not always an option. Suppose your board meets once every month to discuss sensitive issues - how are your board members going to communicate the other 29 days? What if it&#039;s not a billion dollar deal but just millions. What if it&#039;s an emergency and you do not havethe luxury of time? The marginal cost (time and money) of the clean room or even having all team members flying in might be a factor in your decision to switch to encrypted calls.&lt;br&gt;&lt;br&gt;Imagine a scenario where you have people deployed in a developing country handling reconstruction projects. Maybe in a deserted area where it&#039;s pretty hard to have a secure room. Would you trust the network? You bet I would not.&lt;br&gt;&lt;br&gt;More to that point we have seen board members of large companies equipped with military handsets specifically for the reasons I just mentioned. And their usability is atrocious.&lt;br&gt;&lt;br&gt;On your second issue re handsets security you are also spot on. We need to be able to trust the device not just have secure communications. Only manufacturers can address this issue and they currently do it by locking down the devices and signing software but it&#039;s not a silver bullet.&lt;br&gt;I still prefer Cellcrypt to military handsets with 10 year old firmware (which is anyway a civilian solution stripped down of certain functionalities).&lt;br&gt;&lt;br&gt;My 0.02</description>
		<content:encoded><![CDATA[<p>Hi,</p>
<p>just a quick disclaimer: I&#39;m the co-founder of Cellcrypt.</p>
<p>Having said that you&#39;re 100% right on the soundproof room. I have spoken with customers that they have the same setup for their board meetings or emergency rooms. Pretty much they are protected to everything that requires proximity (lip reading, laser microphones etc) or physical access (bugging)</p>
<p>What we do address is that you are constrained to that room and that is not always an option. Suppose your board meets once every month to discuss sensitive issues &#8211; how are your board members going to communicate the other 29 days? What if it&#39;s not a billion dollar deal but just millions. What if it&#39;s an emergency and you do not havethe luxury of time? The marginal cost (time and money) of the clean room or even having all team members flying in might be a factor in your decision to switch to encrypted calls.</p>
<p>Imagine a scenario where you have people deployed in a developing country handling reconstruction projects. Maybe in a deserted area where it&#39;s pretty hard to have a secure room. Would you trust the network? You bet I would not.</p>
<p>More to that point we have seen board members of large companies equipped with military handsets specifically for the reasons I just mentioned. And their usability is atrocious.</p>
<p>On your second issue re handsets security you are also spot on. We need to be able to trust the device not just have secure communications. Only manufacturers can address this issue and they currently do it by locking down the devices and signing software but it&#39;s not a silver bullet.<br />I still prefer Cellcrypt to military handsets with 10 year old firmware (which is anyway a civilian solution stripped down of certain functionalities).</p>
<p>My 0.02</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: patrickjpr</title>
		<link>http://www.mobileindustryreview.com/2009/07/how_secure_are_your_mobile_calls.html/comment-page-1#comment-246502</link>
		<dc:creator>patrickjpr</dc:creator>
		<pubDate>Mon, 03 Aug 2009 14:33:23 +0000</pubDate>
		<guid isPermaLink="false">http://www.mobileindustryreview.com/?p=16519#comment-246502</guid>
		<description>&lt;span class=&quot;topsy_trackback_comment&quot;&gt;&lt;span class=&quot;topsy_twitter_username&quot;&gt;&lt;span class=&quot;topsy_trackback_content&quot;&gt;[client pimping] RT &lt;a href=&quot;http://topsy.com/twitter/rodolfor&quot;&gt;@rodolfor&lt;/a&gt;: Cellcrypt &quot;Not just a bit more secure but SHIT HOT secure&quot; woah http://ow.ly/iVK8&lt;/span&gt;&lt;/span&gt;</description>
		<content:encoded><![CDATA[<p><span class="topsy_trackback_comment"><span class="topsy_twitter_username"><span class="topsy_trackback_content">[client pimping] RT <a href="http://topsy.com/twitter/rodolfor">@rodolfor</a>: Cellcrypt &quot;Not just a bit more secure but SHIT HOT secure&quot; woah <a href="http://ow.ly/iVK8" rel="nofollow">http://ow.ly/iVK8</a></span></span></span></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Rodolfo</title>
		<link>http://www.mobileindustryreview.com/2009/07/how_secure_are_your_mobile_calls.html/comment-page-1#comment-247587</link>
		<dc:creator>Rodolfo</dc:creator>
		<pubDate>Mon, 03 Aug 2009 12:20:57 +0000</pubDate>
		<guid isPermaLink="false">http://www.mobileindustryreview.com/?p=16519#comment-247587</guid>
		<description>&lt;span class=&quot;topsy_trackback_comment&quot;&gt;&lt;span class=&quot;topsy_twitter_username&quot;&gt;&lt;span class=&quot;topsy_trackback_content&quot;&gt;Cellcrypt &quot;Not just a bit more secure but SHIT HOT secure&quot; woah http://ow.ly/iVK8&lt;/span&gt;&lt;/span&gt;</description>
		<content:encoded><![CDATA[<p><span class="topsy_trackback_comment"><span class="topsy_twitter_username"><span class="topsy_trackback_content">Cellcrypt &#8220;Not just a bit more secure but SHIT HOT secure&#8221; woah <a href="http://ow.ly/iVK8" rel="nofollow">http://ow.ly/iVK8</a></span></span></span></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Cellcrypt</title>
		<link>http://www.mobileindustryreview.com/2009/07/how_secure_are_your_mobile_calls.html/comment-page-1#comment-247691</link>
		<dc:creator>Cellcrypt</dc:creator>
		<pubDate>Mon, 03 Aug 2009 12:19:33 +0000</pubDate>
		<guid isPermaLink="false">http://www.mobileindustryreview.com/?p=16519#comment-247691</guid>
		<description>&lt;span class=&quot;topsy_trackback_comment&quot;&gt;&lt;span class=&quot;topsy_twitter_username&quot;&gt;&lt;span class=&quot;topsy_trackback_content&quot;&gt;Mobile Industry Review: How secure are your mobile calls?
 http://ow.ly/iVK8&lt;/span&gt;&lt;/span&gt;</description>
		<content:encoded><![CDATA[<p><span class="topsy_trackback_comment"><span class="topsy_twitter_username"><span class="topsy_trackback_content">Mobile Industry Review: How secure are your mobile calls?<br />
 <a href="http://ow.ly/iVK8" rel="nofollow">http://ow.ly/iVK8</a></span></span></span></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Malcolm Murphy</title>
		<link>http://www.mobileindustryreview.com/2009/07/how_secure_are_your_mobile_calls.html/comment-page-1#comment-239040</link>
		<dc:creator>Malcolm Murphy</dc:creator>
		<pubDate>Fri, 31 Jul 2009 14:14:57 +0000</pubDate>
		<guid isPermaLink="false">http://www.mobileindustryreview.com/?p=16519#comment-239040</guid>
		<description>The issue is not the technology.  It&#039;s never the technology.  How many commercially sensitive conversations have you overheard on a train/in a hotel lobby/etc?&lt;br&gt;&lt;br&gt;Super secure phone line/voice mail/whatever will always be defeated by stupid or naive behaviour. &lt;br&gt;&lt;br&gt;As Mike42 says, if you&#039;re in a multi-bn deal environment, you&#039;d better have your own spooks looking after you.  This kind of solution, neat and cool though it is, just can&#039;t be good enough.</description>
		<content:encoded><![CDATA[<p>The issue is not the technology.  It&#39;s never the technology.  How many commercially sensitive conversations have you overheard on a train/in a hotel lobby/etc?</p>
<p>Super secure phone line/voice mail/whatever will always be defeated by stupid or naive behaviour. </p>
<p>As Mike42 says, if you&#39;re in a multi-bn deal environment, you&#39;d better have your own spooks looking after you.  This kind of solution, neat and cool though it is, just can&#39;t be good enough.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mike42</title>
		<link>http://www.mobileindustryreview.com/2009/07/how_secure_are_your_mobile_calls.html/comment-page-1#comment-239039</link>
		<dc:creator>Mike42</dc:creator>
		<pubDate>Fri, 31 Jul 2009 13:35:50 +0000</pubDate>
		<guid isPermaLink="false">http://www.mobileindustryreview.com/?p=16519#comment-239039</guid>
		<description>The big problem I have with this is: If a deal IS worth Bn&#039;s, and compromising the call could compromise Bn&#039;s, then the call better be &lt;br&gt;&lt;br&gt;a) over milspec cypher kit&lt;br&gt;b) be made in a soundproof, clean (i.e. bug-swept) room &lt;br&gt;c) be made out of line of sight of ANYONE or ANYTHING that could record your face and pass it to a lipreader.&lt;br&gt;d) The recipient likewise must not be compromised by their environment. &lt;br&gt;&lt;br&gt;So - any call made outdoors, or in an office with glass windows, or in a car you don&#039;t own / have had debugged, or within earshot of anyone you don&#039;t 100% trust, is not secure.&lt;br&gt;&lt;br&gt;Plopping an app onto a handset that can also run loads of other apps is not the way. Who&#039;s to say while you were at the pool last week that someone didn&#039;t crack your locker (Â£5 combination lock from Halfords) and install a simple audio recording app that then sent the WAV files to a server somewhere? You&#039;d never know - unless you didn&#039;t have a data plan (unlikely on an iPhone or BB) and anyway, it could make ghost calls/MMS you weren&#039;t aware of.&lt;br&gt;&lt;br&gt;If execs believe they are safe because they use CellCrypt, they need re-educating by their own &#039;Dark Ops&#039; guys.&lt;br&gt;&lt;br&gt;Bottom line: if you think you NEED this solution, then by definition of what it&#039;s installed on and how it gets used it isn&#039;t good enough.&lt;br&gt;&lt;br&gt;/m</description>
		<content:encoded><![CDATA[<p>The big problem I have with this is: If a deal IS worth Bn&#39;s, and compromising the call could compromise Bn&#39;s, then the call better be </p>
<p>a) over milspec cypher kit<br />b) be made in a soundproof, clean (i.e. bug-swept) room <br />c) be made out of line of sight of ANYONE or ANYTHING that could record your face and pass it to a lipreader.<br />d) The recipient likewise must not be compromised by their environment. </p>
<p>So &#8211; any call made outdoors, or in an office with glass windows, or in a car you don&#39;t own / have had debugged, or within earshot of anyone you don&#39;t 100% trust, is not secure.</p>
<p>Plopping an app onto a handset that can also run loads of other apps is not the way. Who&#39;s to say while you were at the pool last week that someone didn&#39;t crack your locker (Â£5 combination lock from Halfords) and install a simple audio recording app that then sent the WAV files to a server somewhere? You&#39;d never know &#8211; unless you didn&#39;t have a data plan (unlikely on an iPhone or BB) and anyway, it could make ghost calls/MMS you weren&#39;t aware of.</p>
<p>If execs believe they are safe because they use CellCrypt, they need re-educating by their own &#39;Dark Ops&#39; guys.</p>
<p>Bottom line: if you think you NEED this solution, then by definition of what it&#39;s installed on and how it gets used it isn&#39;t good enough.</p>
<p>/m</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: mobilegd</title>
		<link>http://www.mobileindustryreview.com/2009/07/how_secure_are_your_mobile_calls.html/comment-page-1#comment-240794</link>
		<dc:creator>mobilegd</dc:creator>
		<pubDate>Fri, 31 Jul 2009 13:35:04 +0000</pubDate>
		<guid isPermaLink="false">http://www.mobileindustryreview.com/?p=16519#comment-240794</guid>
		<description>&lt;span class=&quot;topsy_trackback_comment&quot;&gt;&lt;span class=&quot;topsy_twitter_username&quot;&gt;&lt;span class=&quot;topsy_trackback_content&quot;&gt;How secure are your mobile calls? http://tinyurl.com/lu7aop&lt;/span&gt;
&lt;div class=&quot;topsy_trackback_links&quot;&gt;[&lt;a href=&quot;http://twitter.com/mobilegd/status/2950986429&quot;&gt;Original tweet&lt;/a&gt;, &lt;a href=&quot;http://topsy.com/tb/www.mobileindustryreview.com/2009/07/how_secure_are_your_mobile_calls.html&quot;&gt;Topsy page&lt;/a&gt;]&lt;/div&gt;&lt;/span&gt;</description>
		<content:encoded><![CDATA[<p><span class="topsy_trackback_comment"><span class="topsy_twitter_username"><span class="topsy_trackback_content">How secure are your mobile calls? <a href="http://tinyurl.com/lu7aop" rel="nofollow">http://tinyurl.com/lu7aop</a></span></p>
<div class="topsy_trackback_links">[<a href="http://twitter.com/mobilegd/status/2950986429">Original tweet</a>, <a href="http://topsy.com/tb/www.mobileindustryreview.com/2009/07/how_secure_are_your_mobile_calls.html">Topsy page</a>]</div>
<p></span></span></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: mobilegd</title>
		<link>http://www.mobileindustryreview.com/2009/07/how_secure_are_your_mobile_calls.html/comment-page-1#comment-248104</link>
		<dc:creator>mobilegd</dc:creator>
		<pubDate>Fri, 31 Jul 2009 08:35:04 +0000</pubDate>
		<guid isPermaLink="false">http://www.mobileindustryreview.com/?p=16519#comment-248104</guid>
		<description>&lt;span class=&quot;topsy_trackback_comment&quot;&gt;&lt;span class=&quot;topsy_twitter_username&quot;&gt;&lt;span class=&quot;topsy_trackback_content&quot;&gt;How secure are your mobile calls? http://tinyurl.com/lu7aop&lt;/span&gt;&lt;/span&gt;</description>
		<content:encoded><![CDATA[<p><span class="topsy_trackback_comment"><span class="topsy_twitter_username"><span class="topsy_trackback_content">How secure are your mobile calls? <a href="http://tinyurl.com/lu7aop" rel="nofollow">http://tinyurl.com/lu7aop</a></span></span></span></p>
]]></content:encoded>
	</item>
</channel>
</rss>

