<?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: Where Kim Dotcom and Mega have the edge on Dropbox and Box.net</title>
	<atom:link href="http://gigaom.com/2013/02/02/what-dropbox-and-box-net-can-learn-from-kim-dotcom-and-mega/feed/" rel="self" type="application/rss+xml" />
	<link>http://gigaom.com/2013/02/02/what-dropbox-and-box-net-can-learn-from-kim-dotcom-and-mega/</link>
	<description></description>
	<lastBuildDate>Fri, 24 May 2013 23:12:04 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.com/</generator>
	<item>
		<title>By: Dheeraj</title>
		<link>http://gigaom.com/2013/02/02/what-dropbox-and-box-net-can-learn-from-kim-dotcom-and-mega/#comment-1309389</link>
		<dc:creator><![CDATA[Dheeraj]]></dc:creator>
		<pubDate>Thu, 07 Feb 2013 17:16:10 +0000</pubDate>
		<guid isPermaLink="false">http://gigaom.com/?p=604638#comment-1309389</guid>
		<description><![CDATA[Does anyone know what “store keys locally” means?

Because as far as I can see, Mega is not locked to one computer, and the user has only one key – his password.

What are these multiple ‘keys’? How are these stored locally if the user go to another computer and also login with only the user name and password?]]></description>
		<content:encoded><![CDATA[<p>Does anyone know what “store keys locally” means?</p>
<p>Because as far as I can see, Mega is not locked to one computer, and the user has only one key – his password.</p>
<p>What are these multiple ‘keys’? How are these stored locally if the user go to another computer and also login with only the user name and password?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: SG</title>
		<link>http://gigaom.com/2013/02/02/what-dropbox-and-box-net-can-learn-from-kim-dotcom-and-mega/#comment-1308776</link>
		<dc:creator><![CDATA[SG]]></dc:creator>
		<pubDate>Wed, 06 Feb 2013 16:19:13 +0000</pubDate>
		<guid isPermaLink="false">http://gigaom.com/?p=604638#comment-1308776</guid>
		<description><![CDATA[I really recommend you guys to try BoxCryptor (www.boxcryptor.com). It offers true client-side encryption because the software is always installed locally on the user’s device and the user keeps the control of the security of his data in any cloud. BoxCryptor works with all major cloud storage services and provides an independent source of trust where the cloud storage provider is not responsible for the encryption nor the secure handling of the keys (note: BoxCryptor has no access to the files). Mega’s security has various drawbacks which were discovered by security researchers in the past days such as weak random number generator, weak key derivation easy injection of wrong code, among others ... so the combination of serious implementation flaws and the fact that you still have to put all your trust in Mega, as they will have your files and are in charge of the encryption, makes it a no-go to store sensitive files.]]></description>
		<content:encoded><![CDATA[<p>I really recommend you guys to try BoxCryptor (www.boxcryptor.com). It offers true client-side encryption because the software is always installed locally on the user’s device and the user keeps the control of the security of his data in any cloud. BoxCryptor works with all major cloud storage services and provides an independent source of trust where the cloud storage provider is not responsible for the encryption nor the secure handling of the keys (note: BoxCryptor has no access to the files). Mega’s security has various drawbacks which were discovered by security researchers in the past days such as weak random number generator, weak key derivation easy injection of wrong code, among others &#8230; so the combination of serious implementation flaws and the fact that you still have to put all your trust in Mega, as they will have your files and are in charge of the encryption, makes it a no-go to store sensitive files.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: John Tucker</title>
		<link>http://gigaom.com/2013/02/02/what-dropbox-and-box-net-can-learn-from-kim-dotcom-and-mega/#comment-1308278</link>
		<dc:creator><![CDATA[John Tucker]]></dc:creator>
		<pubDate>Tue, 05 Feb 2013 17:20:10 +0000</pubDate>
		<guid isPermaLink="false">http://gigaom.com/?p=604638#comment-1308278</guid>
		<description><![CDATA[Clients keeping their own keys are nothing new. Many services did it long before MEGA. SpiderOak, Mozy, CrashPlan all offer private keys that stay with the user.]]></description>
		<content:encoded><![CDATA[<p>Clients keeping their own keys are nothing new. Many services did it long before MEGA. SpiderOak, Mozy, CrashPlan all offer private keys that stay with the user.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Sandy Mckinnon</title>
		<link>http://gigaom.com/2013/02/02/what-dropbox-and-box-net-can-learn-from-kim-dotcom-and-mega/#comment-1308237</link>
		<dc:creator><![CDATA[Sandy Mckinnon]]></dc:creator>
		<pubDate>Tue, 05 Feb 2013 16:15:52 +0000</pubDate>
		<guid isPermaLink="false">http://gigaom.com/?p=604638#comment-1308237</guid>
		<description><![CDATA[Andy - If you are interested in scalable next-gen Key management - Please check out SkyKEY and SkyPIN from CertiVox - www.certivox.com - they are currently in Las Vegas launching their SSO solution for the Parallels APS framework as part of the Parallels 2013 Summit - which will allow hosting vendors to offer their services federating the SSO from APS - and with CertiVox&#039;s SkyKEY service handling all the key distribution and management - and SkyPIN giving simple secure multifactor authentication.

It&#039;s coming - you can try it currently at PrivateSky - they can provide this for all cloud &amp; mobile services (including data in motion and at rest somewhere...) Check them out at RSA if you are going at the end of the month.]]></description>
		<content:encoded><![CDATA[<p>Andy &#8211; If you are interested in scalable next-gen Key management &#8211; Please check out SkyKEY and SkyPIN from CertiVox &#8211; <a href="http://www.certivox.com" rel="nofollow">http://www.certivox.com</a> &#8211; they are currently in Las Vegas launching their SSO solution for the Parallels APS framework as part of the Parallels 2013 Summit &#8211; which will allow hosting vendors to offer their services federating the SSO from APS &#8211; and with CertiVox&#8217;s SkyKEY service handling all the key distribution and management &#8211; and SkyPIN giving simple secure multifactor authentication.</p>
<p>It&#8217;s coming &#8211; you can try it currently at PrivateSky &#8211; they can provide this for all cloud &amp; mobile services (including data in motion and at rest somewhere&#8230;) Check them out at RSA if you are going at the end of the month.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Andy Manoske</title>
		<link>http://gigaom.com/2013/02/02/what-dropbox-and-box-net-can-learn-from-kim-dotcom-and-mega/#comment-1307546</link>
		<dc:creator><![CDATA[Andy Manoske]]></dc:creator>
		<pubDate>Mon, 04 Feb 2013 08:29:35 +0000</pubDate>
		<guid isPermaLink="false">http://gigaom.com/?p=604638#comment-1307546</guid>
		<description><![CDATA[Thanks for the comment! A few comments have touched on this, but the novelty in Mega&#039;s cryptography is in key management. Mega has worked particularly hard to design an architecture where users keep their own keys and leave the host with as little information as possible to recover the plaintext from the remotely-stored ciphertext. 

Many of the other approaches on the market employ cryptography where either the key is shared with the host (even if only for a short period of time), information that could be used to recover the key is shared with the host, or the key is generated in a way that could possibly be exploited in a partial information attack by someone with visibility into the host / the host itself.]]></description>
		<content:encoded><![CDATA[<p>Thanks for the comment! A few comments have touched on this, but the novelty in Mega&#8217;s cryptography is in key management. Mega has worked particularly hard to design an architecture where users keep their own keys and leave the host with as little information as possible to recover the plaintext from the remotely-stored ciphertext. </p>
<p>Many of the other approaches on the market employ cryptography where either the key is shared with the host (even if only for a short period of time), information that could be used to recover the key is shared with the host, or the key is generated in a way that could possibly be exploited in a partial information attack by someone with visibility into the host / the host itself.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: me</title>
		<link>http://gigaom.com/2013/02/02/what-dropbox-and-box-net-can-learn-from-kim-dotcom-and-mega/#comment-1307509</link>
		<dc:creator><![CDATA[me]]></dc:creator>
		<pubDate>Mon, 04 Feb 2013 03:12:28 +0000</pubDate>
		<guid isPermaLink="false">http://gigaom.com/?p=604638#comment-1307509</guid>
		<description><![CDATA[There were employees of the US government using Megaupload for file storage. You should tell them that their files were illegal.  They probably have no idea.  I had legitimate files on megaupload, but according to Jill I guess my files were illegal too.  Too funny.

Anyway, as for illegal files, simple Google searches will find that for you very easily and quickly.  I wonder when the US govt will take Google down.]]></description>
		<content:encoded><![CDATA[<p>There were employees of the US government using Megaupload for file storage. You should tell them that their files were illegal.  They probably have no idea.  I had legitimate files on megaupload, but according to Jill I guess my files were illegal too.  Too funny.</p>
<p>Anyway, as for illegal files, simple Google searches will find that for you very easily and quickly.  I wonder when the US govt will take Google down.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Rich</title>
		<link>http://gigaom.com/2013/02/02/what-dropbox-and-box-net-can-learn-from-kim-dotcom-and-mega/#comment-1307388</link>
		<dc:creator><![CDATA[Rich]]></dc:creator>
		<pubDate>Sun, 03 Feb 2013 17:10:47 +0000</pubDate>
		<guid isPermaLink="false">http://gigaom.com/?p=604638#comment-1307388</guid>
		<description><![CDATA[Come on, Jill. GigaOm (or actually, the author Andy Manoske) cannot say that the original metaupload site had copyrighted software, because that would expose the author to a legal liability for accusing someone of unlawful activity. That is why publications use the word &quot;alleged,&quot; or similar terms. Your comment is a little naive.]]></description>
		<content:encoded><![CDATA[<p>Come on, Jill. GigaOm (or actually, the author Andy Manoske) cannot say that the original metaupload site had copyrighted software, because that would expose the author to a legal liability for accusing someone of unlawful activity. That is why publications use the word &#8220;alleged,&#8221; or similar terms. Your comment is a little naive.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Nhick</title>
		<link>http://gigaom.com/2013/02/02/what-dropbox-and-box-net-can-learn-from-kim-dotcom-and-mega/#comment-1307349</link>
		<dc:creator><![CDATA[Nhick]]></dc:creator>
		<pubDate>Sun, 03 Feb 2013 14:44:31 +0000</pubDate>
		<guid isPermaLink="false">http://gigaom.com/?p=604638#comment-1307349</guid>
		<description><![CDATA[Hmm, so we should expect another blockbuster hit on this one aight?]]></description>
		<content:encoded><![CDATA[<p>Hmm, so we should expect another blockbuster hit on this one aight?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: notthefbi</title>
		<link>http://gigaom.com/2013/02/02/what-dropbox-and-box-net-can-learn-from-kim-dotcom-and-mega/#comment-1307344</link>
		<dc:creator><![CDATA[notthefbi]]></dc:creator>
		<pubDate>Sun, 03 Feb 2013 14:12:18 +0000</pubDate>
		<guid isPermaLink="false">http://gigaom.com/?p=604638#comment-1307344</guid>
		<description><![CDATA[Jill, how much do you make per comment?]]></description>
		<content:encoded><![CDATA[<p>Jill, how much do you make per comment?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Chad</title>
		<link>http://gigaom.com/2013/02/02/what-dropbox-and-box-net-can-learn-from-kim-dotcom-and-mega/#comment-1307322</link>
		<dc:creator><![CDATA[Chad]]></dc:creator>
		<pubDate>Sun, 03 Feb 2013 12:18:39 +0000</pubDate>
		<guid isPermaLink="false">http://gigaom.com/?p=604638#comment-1307322</guid>
		<description><![CDATA[According to Mega, they are only deduplicating post-encryption, so that part of their TOS functionally only applies to duplicate files uploaded by the same person or files that are shared from one account to another.

http://mega.co.nz/#blog_3]]></description>
		<content:encoded><![CDATA[<p>According to Mega, they are only deduplicating post-encryption, so that part of their TOS functionally only applies to duplicate files uploaded by the same person or files that are shared from one account to another.</p>
<p><a href="http://mega.co.nz/#blog_3" rel="nofollow">http://mega.co.nz/#blog_3</a></p>
]]></content:encoded>
	</item>
</channel>
</rss>