Showing posts with label Mega Kim Dotcom. Show all posts
Showing posts with label Mega Kim Dotcom. Show all posts

Sunday, January 27, 2013

MEGA's First Week - A Retrospective - Future Is Open Source

how to create an account using mega 50gb free storage

January 26th 2013


It's been seven busy days for us since MEGA went live. As millions of users were hitting 50,000 freshly written and barely tested lines of code and dozens of newly installed servers, teething troubles were inevitable - it took us almost 72 hours to resolve the major bottlenecks, and we would like to apologize to all users who were affected.

As expected, the public debate about MEGA revolves primarily around our cryptographic security model and can be classified into five categories:
  • Actual bugs. Two (an XSS hole and the invalid use of CBC-MAC as a secure hash) were reported by the community so far and fixed swiftly. To all the bright minds going through our amorphous code: Thank you for your efforts! We will make our JavaScript more readable and launch a bug bounty program shortly.
  •  
  • Design flaws exacerbating the potential impact of weak user passwords. We acknowledge that our current approach is based on the assumption that all of our users choose strong passwords, which is probably a bit naive. We are going to improve the sign-up interface (better user education and rejection of overly weak passwords). We'll also reduce the offline password cracking risk for users who do use weak passwords and fall victim to someone intercepting their e-mail or obtaining their user record from our central database.
  •  
  • Weak random number generation: We have added WebKit's crypto.getRandomValues() into the mix and will collect mouse/keyboard timing entropy explicitly before generating the RSA key pair rather than informing the user that we are doing so only after the generation has already started.
  •  
  • Deduplication - clause 8 of our Terms of Service has caused some confusion and concern. The reality is quite harmless: We deduplicate based on the full encrypted file. That's it.
  •  
  • Polemic in the "if you can break SSL, you can break MEGA" category. No comment.
top cloud storage alternatives dropbox

 

 Development roadmap

January 18th 2013Time flies when building a website, and unfortunately, half of the launch feature list that we envisioned when we started implementing MEGA back in September has now turned into a post-launch development roadmap. These are the essentials that we will work on next:
Developer documentation enhancements:
  • Properly reformat and comment the JavaScript reference implementation so that it becomes more readable
  • Add missing command-specific documentation to the API reference
File transfer queue enhancements:
  • Vertical resizing
  • Drag & Drop to modify transfer sequence
  • Multiselect
  • Clicking on a pending transfer navigates to/marks the source file or the target folder
  • Stop/continue buttons
File manager enhancements:
  • Re-implement from scratch without underlying third-party UI framework for better performance
  • Adaptively eliminate the leftmost file path buttons at the top to maintain visibility of the upload and search buttons (we have a hack in place for this, but it only works in Chrome)
  • "Properties" option in the file context menu
Collaboration feature enhancements:
  • MEGA user-to-user messaging with file attachments, plus external RFC 4880/OpenPGP and S/MIME gateway for secure off-site e-mail communication
  • MEGA user-to-user instant messaging
  • Exported link enhancements
  • Allow for the creation of folder links (with associated crypto key) which then display the folder content live
  • Secure unauthenticated delivery web widget
  • Allow unauthenticated users to securely deliver files to MEGA users' inboxes, e.g. to submit very large files to print shops
Filesystem enhancements:
  • Activate storing all block MACs on the server (encrypted) after an upload to allow for integrity-checked partial reading. Right now, the file has to be downloaded fully to be checked.
  • Enable forking encrypted time-stamped delta file support to allow for random writing to existing files with full rollback capability
SDK enhancements
  • Complete the API documentation
  • Provide client libraries in various languages
Client applications
  • A Windows filesystem mount is currently in beta and will be available shortly
  • Linux/MacOS X filesystem mounts
  • Mobile access
  • Sync tools for all major platforms
Integrated on-site applications
  • Calendar
  • Word processing
  • Spreadsheet
MEGA as a local "appliance"
  • Load a third-party audited version of the MEGA JavaScript files from a machine that you control
  • Be immune against new bugs of any kind

Kim Dotcom wants to encrypt half of the Internet to end government surveillance (RT INTERVIEW) Mega Former Megalupload IS Pushing Browsers To It's Limits

the battle for internet privacy


MEGA pushes the browser to its limits, and these limits vary. While it does work with all major current browsers, there are some weighty feature and performance differences:

Google Chrome: The leading browser, by far. It implements the proposed HTML5 FileSystem API, allowing for fancy features such as recursive folder uploads and efficient downloads. Caveats: Requires user permission to batch-write files after a few unattended completed downloads (for security reasons, and only once per session). Slightly anaemic text rendering.

Internet Explorer 10: A solid, modern browser with blazing JavaScript performance (even exceeding Chrome's). However, until Microsoft fixes a memory leak in the Blob saving functionality, you have to close and reopen the MEGA tab every couple of hundred megabytes of inbound file transfer. And, until Microsoft implements disk-based Blobs or Chrome's FileWriter API, memory usage for a file download peaks at twice the file's size - hardly efficient.

Mozilla Firefox 18: Carefully avoids providing any API that would allow writing files from JavaScript.

Safari 6: No JavaScript file writing, either.

Internet Explorer 9: Lacks all essential features required for MEGA: File I/O, Web Workers, ArrayBuffers, and binary cross-domain HTTP access. Nice text rendering, though.

Opera: No JavaScript file writing and exceedingly slow JavaScript crypto operations.
Conclusion: If you are planning on using MEGA frequently, there is currently no alternative to using the most advanced browser currently in existence - Google Chrome.
Related Posts Plugin for WordPress, Blogger...