According to MEGAs developer site the file’s at MEGA are encrypted with 128 bit AES by the client. The 2048 bit RSA key is used for the coming secure instant messaging and email functions.

(Seems DISQUS has ignored my last posting attempt, so I post it again.)

According to MEGA’s developer site the file’s at MEGA are encrypted with 128 bit AES by the client. The 2048 bit RSA key is used for the coming secure instant messaging and email functions.

(Seems DISQUS has ignored my last posting attempt, so I post it again…)

But if a user wishes to share one of his files his PC can locally extract the key from his master-file using his password and then attach the key to the file link. The result then looks like:

https://mega.co.nz/#!FileID!FileKey

Thanks to the “#”-construct the file key also isn’t transferred to the MEGA-servers if you open the link because “#” is a local HTML-anchor that is used locally by the Browser.

According to MEGA’s developer site the file’s at MEGA are encrypted with 128 bit AES by the client. The 2048 bit RSA key is used for the coming secure instant messaging and email functions.

But this is quite clumsy and not very user-friendly. In contrast to Google and Skydrive MEGA has an already build in client-side AES encryption.

Also Google is know for snooping through the user’s personal data (automatical reading of gmail mails for advertisement targeting and so on…). On MEGA this is thanks to client-side encryption even technically impossible.

If you loose it and have not made a backup yourself, you’re screwed, just like you would have encrypted your stuff manually.

Files that were already encrypted by some other encryption mechanism logically get encrypted a second time (so they have then 2 layers of encryption).