<?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/"
	xmlns:georss="http://www.georss.org/georss" xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#" xmlns:media="http://search.yahoo.com/mrss/"
		>
<channel>
	<title>Comments on: Cellcrypt &#8211; Secure Voice for the Blackberry</title>
	<atom:link href="http://agilityloop.com/2009/05/15/cellcrypt-secure-voice-for-the-blackberry/feed/" rel="self" type="application/rss+xml" />
	<link>http://agilityloop.com/2009/05/15/cellcrypt-secure-voice-for-the-blackberry/</link>
	<description>The musings of the agile on the world of tech and government</description>
	<lastBuildDate>Thu, 26 Aug 2010 19:39:39 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.com/</generator>
	<item>
		<title>By: Kevin Heald</title>
		<link>http://agilityloop.com/2009/05/15/cellcrypt-secure-voice-for-the-blackberry/#comment-16</link>
		<dc:creator>Kevin Heald</dc:creator>
		<pubDate>Mon, 18 May 2009 13:03:44 +0000</pubDate>
		<guid isPermaLink="false">http://agilityloop.wordpress.com/?p=23#comment-16</guid>
		<description>Totally understand, and I figured you all could access the CAC or any smart card...the interfaces are pretty standard.  

The SME-PED will always be behind commercial devices for the reasons you mentioned.  Sometimes I do wonder who really needs Type 1 and who can make do with something like your solution.  

Either way, thx for the comment!</description>
		<content:encoded><![CDATA[<p>Totally understand, and I figured you all could access the CAC or any smart card&#8230;the interfaces are pretty standard.  </p>
<p>The SME-PED will always be behind commercial devices for the reasons you mentioned.  Sometimes I do wonder who really needs Type 1 and who can make do with something like your solution.  </p>
<p>Either way, thx for the comment!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Rodolfo</title>
		<link>http://agilityloop.com/2009/05/15/cellcrypt-secure-voice-for-the-blackberry/#comment-15</link>
		<dc:creator>Rodolfo</dc:creator>
		<pubDate>Sat, 16 May 2009 00:55:49 +0000</pubDate>
		<guid isPermaLink="false">http://agilityloop.wordpress.com/?p=23#comment-15</guid>
		<description>One last thing, SME-PED still uses CSD and not IP which means that 1- the signaling call data is not secure 2- has an horrible performance in terms of network availability and voice latency.</description>
		<content:encoded><![CDATA[<p>One last thing, SME-PED still uses CSD and not IP which means that 1- the signaling call data is not secure 2- has an horrible performance in terms of network availability and voice latency.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Rodolfo</title>
		<link>http://agilityloop.com/2009/05/15/cellcrypt-secure-voice-for-the-blackberry/#comment-14</link>
		<dc:creator>Rodolfo</dc:creator>
		<pubDate>Sat, 16 May 2009 00:49:26 +0000</pubDate>
		<guid isPermaLink="false">http://agilityloop.wordpress.com/?p=23#comment-14</guid>
		<description>Hi Kevin, thanks for your post about Cellcrypt.

Plugging into an external PKI is certainly feasible - we already assumed that larger customers will want to use their own. This also means that implementing the DoD CAC would be a possibility. CAC is just x.509 and there is already out a Bluetooth smart card reader for the BlackBerry.

Re SME-PED there is a fundamental difference in the goal we are trying to achieve. The SME-PED is a Type 1 encryption device, meaning that not just the communications are secure but the entire device (meaning both software and hardware) are certified to be secure and this include anti-tampering and TEMPEST shielding. This means that it has very long development cycles and has an endemic &quot;old generation&quot; feel to it.
SME-PED is certified to carry information that is classified as Top Secret while Cellcrypt was designed for (Secret, Confidential, Unclassified but Sensitive).

If you look at the bigger picture there are approx 30k-50k users of Type 1 devices in the Federal Government... and everybody else is not using any voice security whatsoever. We basically wanna fill that middle market without replacing your phone with a brick.

Rodolfo (co-founder of Cellcrypt)</description>
		<content:encoded><![CDATA[<p>Hi Kevin, thanks for your post about Cellcrypt.</p>
<p>Plugging into an external PKI is certainly feasible &#8211; we already assumed that larger customers will want to use their own. This also means that implementing the DoD CAC would be a possibility. CAC is just x.509 and there is already out a Bluetooth smart card reader for the BlackBerry.</p>
<p>Re SME-PED there is a fundamental difference in the goal we are trying to achieve. The SME-PED is a Type 1 encryption device, meaning that not just the communications are secure but the entire device (meaning both software and hardware) are certified to be secure and this include anti-tampering and TEMPEST shielding. This means that it has very long development cycles and has an endemic &#8220;old generation&#8221; feel to it.<br />
SME-PED is certified to carry information that is classified as Top Secret while Cellcrypt was designed for (Secret, Confidential, Unclassified but Sensitive).</p>
<p>If you look at the bigger picture there are approx 30k-50k users of Type 1 devices in the Federal Government&#8230; and everybody else is not using any voice security whatsoever. We basically wanna fill that middle market without replacing your phone with a brick.</p>
<p>Rodolfo (co-founder of Cellcrypt)</p>
]]></content:encoded>
	</item>
</channel>
</rss>
