Showing posts with label megaupload. Show all posts
Showing posts with label megaupload. Show all posts

Friday, March 1, 2013

Exposed: Hadopi France Or The New Version Of ACTA Is Fighting Against Streaming And Direct Download Sites. They Don't Want You To Get Free Education And Have A Better Life - France Democracy Collapsing Damages The Freedom Of Expression, The Protection Of Privacy And The Right To A Fair Trial. - Social Mass Awakening

there is enough for everyone, no need to compete anymore, good advice

HADOPI law

From Wikipedia, the free encyclopedia
Jump to: navigation, search
The French HADOPI law or Creation and Internet law (French: Haute Autorité pour la diffusion des œuvres et la protection des droits sur internet,[1] "law promoting the distribution and protection of creative works on the internet") was introduced during 2009, providing what is known as a graduated response as a means to encourage compliance with copyright laws. HADOPI is the acronym of the government agency created to administer it.

Contents

Legislative passage

Despite strong backing from President Nicolas Sarkozy, the bill was rejected by the French National Assembly on 9 April 2009.[2][3][4] The French government asked for reconsideration of the bill by the French National Assembly and it was adopted on 12 May 2009 by the assembly,[5] and on 13 May 2009 by the French Senate.
Debate included accusations of dubious tactics made against the promoters of the bill. There were complaints that the government's official website misrepresented the bill,[6] that the French Wikipedia pages on it were falsified by the Ministry of Culture on 14 February 2009.[7] and a "petition of 10,000 artists" in support of the bill was questioned as allegedly fraudulent.[8]

Timeline

  • The bill was presented to the French Senate by the government on June 18, 2008.
  • On October 23, 2008, the government shortened the debate by making the bill a matter of urgency, meaning it could be read only once in each chamber, under art. 45 of the French constitution.
  • The bill was adopted by the Senate on October 30, 2008.
  • The bill was presented to the Assembly on March 11th, 2009 where it was amended and the amended version adopted on April 2, 2009.
  • Since the two legislative chambers had now adopted different versions, a parliamentary commission (seven members of the Senate and seven members of the Assembly) was constituted on April 7, 2009, mandated to produce a common text to be voted on by both chambers without further debate.
  • The resultant bill was unanimously adopted by the Senate on April 9, 2009. On the same day, it was defeated in the Assembly (21-15), a consequence of absenteeism on the part of French socialist party MPs who later explained themselves in an open letter to the newspaper Libération.[9] published on April 27, 2009; coauthored by Jean-Marc Ayrault, Patrick Bloche, François Brottes, Corinne Erhel, Michel Françaix, Jean-Louis Gagnaire, Didier Mathus, Sandrine Mazetier, Christian Paul
  • The bill was re-presented to the National Assembly on April 29 when 499 amendments were moved, most of which were rejected[10][dead link]
  • The amended bill was adopted by the Assembly on May 12, 2009 (296-233). All present French socialist party members voted against it except Jack Lang
  • The Senate voted in favor of the bill on May 13, (189-14), all senators of the socialist party abstaining, except Samia Ghali.
  • On May 17, members of the National Assembly contested the constitutionality of the law and submitted it to the Constitutional Council for examination.
  • On June 10, the Constitutional Council declared the main part of the bill unconstitutional, therefore making it useless. The council found that the law violated the 1789 Declaration of the Rights of Man and of the Citizen, and in particular presumption of innocence, separation of powers and freedom of speech.[11] [12]
  • On 22 October 2009, the Constitutional Council approved a revised version of HADOPI, requiring judicial review before revoking a person's internet access, but otherwise resembling the original requirements.[13]

Details of the law

Government agency

The law creates a government agency called Haute Autorité pour la Diffusion des Œuvres et la Protection des Droits sur Internet (HADOPI) (English: the High Authority for Transmission of Creative Works and Copyright Protection on the Internet); replacing a previous agency, the ARMT (Regulation of Technical Measures Authority) created by the DADVSI law.[14]
The new government agency is headed by a board of nine members, three appointed by the government, two by the legislative bodies, three by judicial bodies and one by the Conseil supérieur de la propriété littéraire et artistique (Superior Council of Artistic and Literary Property), a government council responsible to the French Ministry of Culture.[15] The agency is vested with the power to police Internet users.

Mandate

To ensure that internet subscribers "screen their internet connections in order to prevent the exchange of copyrighted material without prior agreement from the copyright holders" (Art. L. 336-3 of the bill). HADOPI also retains mandates previously attributed to the ARMT.

Enforcement

On receipt of a complaint from a copyright holder or representative, HADOPI may initiate a 'three-strike' procedure:
  • (1) An email message is sent to the offending internet access subscriber, derived from the IP address involved in the claim. The email specifies the time of the claim but neither the object of the claim nor the identity of the claimant.
The ISP is then required to monitor the subject internet connection. In addition, the internet access subscriber is invited to install a filter on his internet connection.
If, in the 6 months following the first step, a repeat offense is suspected by the copyright holder, his representative, the ISP or HADOPI, the second step of the procedure is invoked.
  • (2) A certified letter is sent to the offending internet access subscriber with similar content to the originating email message.
In the event that the offender fails to comply during the year following the reception of the certified letter, and upon accusation of repeated offenses by the copyright holder, a representative, the ISP or HADOPI, the third step of the procedure is invoked.
  • (3) The ISP is required to suspend internet access for the offending internet connection, that which is the subject of the claim, for a specified period of from two months to one year.
The internet access subscriber is blacklisted and other ISPs are prohibited from providing an internet connection to the blacklisted subscriber. The service suspension does not, however, interrupt billing, and the offending subscriber is liable to meet any charges or costs resulting from the service termination.
Appeal to a court is possible only during the third phase of the action (after the blocking of internet access) and an appeal can result in shortening but not cancellation of the blocking. The burden of proof is on the appellant.
According to the CNIL, action under the HADOPI law does not exclude separate prosecution under the French code of Intellectual Property,[16] particularly its articles L331-1 or L335-2, or limit a claimant's other remedies at law. (See CNIL opinion, below).

Background

Implementation of the European Copyright Directive resulted in the French DADVSI law which has been in force since 2007, creating the crime of lack of screening of Internet connections in order to prevent exchange of copyrighted material without prior agreement from the copyright holders (art. L335.12).[17] The DADVSI law did not prescribe any punishment. It has been partially invalidated by the Constitutional Council of France's rejection of the principle of escalation,[18] and retains only the crime of copyright-infringement, punishable by up to 3 years' prison and a fine of up to €300,000.


The HADOPI law is supposed to address the concerns of the Constitutional Council of France, in addition to replacing the DADVSI law, which has yet to be enforced.

Olivennes report and Elysée agreement

On September 5, 2007, the French Minister of Culture, Christine Albanel asked the CEO of the major French entertainment retailer (Fnac), Denis Olivennes, to lead a task force to study a three-strike sanction, to conform with the ruling of the French Constitutional Council. After consulting representatives of the entertainment industry, internet service providers and consumer associations, the Olivennes committee reported to the Minister on November 23.[19] The report was signed by 40 companies at the Elysée and presented as the "Olivennes agreement". It was later renamed the "Elysée agreement".
The HADOPI law is the implementation of the Olivennes report, supported by the Olivennes agreement, in which representatives of the entertainment and media industries gave their assent to the law's enforcement procedures. Nevertheless some companies, notably the ISPs Orange and Free, later dissented from the agreement. [20]

Lobbying for the bill

Owing to its controversial nature, the bill became a subject of intense campaigning in various media, which was redoubled after its parliamentary defeat on April 9, 2009.

Head of state

On October 4, 2008, President Nicolas Sarkozy, a personal supporter of the law, interceded with the president of the European Commission regarding the non-scheduling of the then Amendment 138 (see Amendment 46 (previously 138)) of the Telecoms Package susceptible to invalidate the law. The European Commission rejected his representation on October 6, 2008.

Government

The French government created a promotional website in support of the country's entertainment industry. The content of the website was criticised as misleading.[21]
It was also alleged that French Wikipedia pages relative to HADOPI were edited by the Ministry of Culture on February 14, 2009.[22]

Entertainment industry

SACEM and other entertainment industry players mounted a petition of "10,000 artists" in support of the HADOPI law. The list has been challenged on several grounds:
  • Many signatories are said to be unconnected with artistic activities ascribed to them
  • Some signatories are bogus or fictitious, an example being Paul Atreides.[23]
  • Some artists listed as signatories have denied that they support it.[24]

Lobbying against the bill

Consumer associations

The leading French consumer association UFC Que Choisir has positioned itself against the law and has set up a website to support opposition.[25]
A group called La Quadrature du Net is a strong lobbyist against the law.[26]
Following an open letter in the newspaper Libération[27][dead link] signed by Chantal Akerman, Christophe Honoré, Jean-Pierre Limosin, Zina Modiano, Gaël Morel, Victoria Abril, Catherine Deneuve, Louis Garrel, Yann Gonzalez, Clotilde Hesme, Chiara Mastroianni, Agathe Berman and Paulo Branco producteurs which was published on May 7, 2009, and co-authored notably by Victoria Abril and Catherine Deneuve, an informal group has been constituted under the name Creation Public Internet[28] and is composed of UFC Que Choisir, La Quadrature du Net, some syndicated artists and the Internet Society.
On March 12, 2009, the British Featured Artists Coalition publicised its opposition to the principle of the HADOPI law.[29]

Political groups' positions

With the exception of the French Green Party who campaigned against the law, other political groups represented in the legislative chambers were not active lobbying for or against the law, though individual members did so. The French Socialist Party was probably the most divided. While it initially favored the law (voted yes in the Senate's first reading), it was chiefly responsible for the surprise rejection of the bill after the first reading in the National Assembly, as well as requesting the Constitutional Council's ruling. The Pirate Party (France) although not represented in the legislative chambers also campaigned against the law.

Logo incident

Shortly after HADOPI's agency logo was presented to the public by Minister of Culture and Communication Frédéric Mitterrand, it was revealed that the logo used an unlicensed font. The font was created by typeface designer Jean François Porchez, and is owned by France Télécom. The design agency that drew the logo, Plan Créatif, admitted to using the font by mistake and the logo was redone with another font.[30]

See also

References

  1. ^ "Projet de loi favorisant la diffusion et la protection de la création sur Internet" (in French). French Senate.
  2. ^ "French reject internet piracy law'". BBC News Online. 9 April 2009.
  3. ^ Davies, Lizzy (9 April 2009). "French MPs reject controversial plan to crack down on illegal downloaders". Guardian Unlimited (London).
  4. ^ Bremner, Charles (2 April 2009). "Setback for Sarkozy as French parliament rejects controversial internet law". Times Online (London).
  5. ^ "Lawmakers adopt Internet anti-piracy bill". France 24. 12 May 2009.
  6. ^ "Jaimelesartistes.fr, Albanel explique pourquoi ca-va-couper.fr" (in French). PC Inpact. 31 October 2008.
  7. ^ "Comment Albanel «arrange» Hadopi dans Wikipedia" (in French). 11 May 2009.
  8. ^ Saulnier, Julie (15 April 2009). "Hadopi: couacs autour de la pétition des 10 000 artistes" (in French). L'Express.
  9. ^ (French) [1] Libération April 27, 2009
  10. ^ (French) [2]
  11. ^ see Lucchi, N., Access to Network Services and Protection of Constitutional Rights: Recognizing the Essential Role of Internet Access for the Freedom of Expression (February 6, 2011). Cardozo Journal of International and Comparative Law (JICL), Vol. 19, No. 3, 2011. Available here
  12. ^ "French Constitutional Council: Decision n° 2009-580 of June 10th 2009—Act furthering the diffusion and protection of creation on the Internet" (in English). 10 June 2009. at French Constitutional Council
  13. ^ Pfanner, Eric (22 October 2009). "France Approves Wide Crackdown on Net Piracy". New York Times.
  14. ^ (French) [3]
  15. ^ (French) [4]
  16. ^ (French) [5]
  17. ^ (French) Article L335-12 Code de la propriété intellectuelle, Legifrance
  18. ^ (French) [6]
  19. ^ (French) [7]
  20. ^ (French) [8]
  21. ^ (French) Jaimelesartistes.fr, Albanel explique pourquoi ca-va-couper.fr at PCINpact.com
  22. ^ (French) Comment Albanel «arrange» Hadopi dans Wikipedia at Marianne2, 11 May 2009
  23. ^ (French) La liste des 10 000 signataires at pcinpact.com, 15 April 2009
  24. ^ (French) Hadopi: couacs autour de la pétition des 10 000 artistes at L'Express, 15 April 2009
  25. ^ (French) [9]
  26. ^ Items on HADOPI
  27. ^ (French) [10]
  28. ^ Qui sommes nous? at Creation Public Internet
  29. ^ Akbar, Arifa (2009-03-12). "It's not a crime to download, say musicians". The Independent (London). Retrieved 2010-05-04.
  30. ^ "Anti-piracy agency's logo broke copyright". The Daily Telegraph (London). 2010-01-12. Retrieved 2010-05-04.

Source: https://en.wikipedia.org/wiki/HADOPI_law

Hadopi and Internet Intermediaries: No to a French ACTA!



Paris, 26 February 2013 – Hadopi, the French "three strikes" administration, released yesterday a report [fr] on the fight against streaming and direct download sites. It advocates for the establishment of measures bearing a close resemblance to those of ACTA and the US SOPA bill, both shelved following a strong citizen mobilization for the defense of fundamental freedoms. Currently confined to the fight against file sharing between individuals, Hadopi now wants to extend its control to Internet intermediaries such as hosting services, search engines, Internet service providers or online payment services. Doing so, could only lead them to actively monitor content shared on the Net, with unavoidable collateral damage to freedom of expression, the protection of privacy and the right to a fair trial.

European law clearly states that hosting services cannot be forced to engage in general surveillance of content1. In its report, Hadopi suggests circumventing this limitation by encouraging Internet access and service providers to implement pro-active censorship measures as part of commercial agreements signed with industrial actors. Platforms that refuse to accept these new requirements could face domain name confiscation or censorship by public authorities. The report also proposes actions against search engines to delist given websites or to use censorship systems to block access to these. These schemes mirror the abusive provisions denounced in ACTA and SOPA: increasing Internet Intermediaries' liability, bypassing the judicial authority and moving towards contractual forms of online communication control, leading in turn to private censorship of the Internet.

La Quadrature du Net restates that the best way to fight against for-profit copyright infringement is to legalize non-market sharing between individuals within a clearly defined scope, in order to promote decentralized sharing (peer-to-peer) at the expense of (for-profit) centralized streaming or direct download platforms. To keep advocating for a blind war on sharing, as the Hadopi does, with no distinction between these different practices, will inevitably lead to a repressive spiral detrimental to fundamental freedoms. This report is all the more worrying that it reflects the approach of the working group lead by Pierre Lescure (former CEO of Canal +, major TV station owned by Universal) currently advising the French government on the future of Hadopi. This working group seems to be moving towards means to fight for-profit copyright infringement inspired by ACTA or the American SOPA bill, that is to say, directly inspired by the entertainment industry.

“The French government would be foolish to ignore the previous rejection of ACTA and SOPA. Citizens have shown that they are capable of mobilizing when an unfair, dangerous, and disproportionate approach to copyright threatens their freedoms. The same causes produce the same effects: those who sow ACTA shall reap the citizen whirlwind!” declared Jérémie Zimmermann, spokesperson for citizen advocacy group La Quadrature du Net.
To get more information and discuss this, you can visit our forum.
Source: http://www.laquadrature.net/en/hadopi-and-internet-intermediaries-no-to-a-french-acta 
 

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.

Mega Winner: The cloud storage market is dominated by players that do not take advantage of cryptography beyond HTTPS and server-side encryption.

freedom free journalists stage 1024 encryption

A word on cryptography

January 22nd 2013The cloud storage market is dominated by players that do not take advantage of cryptography beyond HTTPS and server-side encryption. Since we set out to improve this rather dissatisfying situation three days ago, some news outlets have made attempts to dismantle our crypto architecture. Frankly, we were not too impressed with the results and would like to address the points that were raised:
ars technica: "Megabad: A quick look at the state of Mega's encryption"

"The key used to encrypt your Mega files and folders is stored on Mega's servers, rather than on your local computer."

This is correct - the only key that MEGA requires to be stored on the user side is the login password, in the user's brain. This password unlocks the master key, which in turn unlocks the file/folder/share/private keys.

"It is telling that there appears to be no password recovery mechanism anywhere in the Mega or log-on screens, nor any method of changing your password in the user control panel." Because the master AES-128 key is encrypted using your password, remembering the password is vital. Losing it means you don't just lose the ability to log on to the service - you lose the ability to decrypt your files, period.

This is correct (and comes as no surprise) - however, this will change in the near future:
  • A password change feature will re-encrypt the master key with your new password and update it on our servers
  • A password reset mechanism will allow you to log back into your account, with all files being unreadable. Now, if you have any pre-exported file keys, you can import them to regain access to those files. On top of that, you could ask your share peers to send you the share-specific keys, but that's it - the remainder of your data appears as binary garbage until you remember your password.
"Without adding entropy, the "random" primes generated by math.random for use as RSA keys are really only pseudo-random and can be guessed."
This is correct - and quite a strange statement to make after conceding that mouse and keyboard entropy are indeed used to enhance Math.random(). We will, however, add a feature that allows the user to add as much entropy manually as he sees fit before proceeding to the key generation.

[On deduplication] "Whatever the underlying method, the fact that block deduplication exists is a blow against the "see no evil" approach taken by Mega."

Fact #1: Once this feature is activated, chunk MACs will indeed be stored on the server side, but they will of course be encrypted (and we will not use ECB!). Fact #2: MEGA indeed uses deduplication, but it does so based on the entire file post-encryption rather than on blocks pre-encryption. If the same file is uploaded twice, encrypted with the same random 128-bit key, only one copy is stored on the server. Or, if (and this is much more likely!) a file is copied between folders or user accounts through the file manager or the API, all copies point to the same physical file.

Forbes: Researchers Warn: Mega's New Encrypted Cloud Doesn't Keep Its Megasecurity Promises
"So Mega, or anyone else who gains control of the Mega server sending the crypto algorithms, can turn off that encryption or steal the user's private key, which would allow decryption of all past and future uploads."

Correct. Fact #1: Our FAQ states exactly that and warns people that do not trust us to refrain from logging into the site (but they could, in theory, still safely use MEGA through client apps from vendors they trust). Fact #2: Any software maker offering online application updates is able to plant Trojan code into specific targets' computers, with much more far-reaching consequences.

"If you can break SSL, you can break MEGA."

Yes. But if you can break SSL, you can break a lot of things that are even more interesting than MEGA.

"To make matters worse, Mega's SSL server seems to use weak 1024-bit encryption, rather than the 2048-bit encryption considered the minimum standard by many cryptographers for a decade. (This 2004 study, for instance, that declared 1024-bit keys would only be secure until 2006.)"

Fact #1: https://mega.co.nz/ uses 2048-bit encryption. Fact #2: https://*.static.co.nz/ uses 1024-bit encryption. Fact #3: All active content loaded from these "insecure" static servers is integrity-checked by JavaScript code loaded from the "secure" static server, rendering manipulation of the static content or man-in-the-middle attacks ineffective. The only reason why HTTPS is supported/used at all is that most browsers don't like making HTTP connections from HTTPS pages. And, using more than 1024 bit would just waste a lot of extra CPU time on those static servers. Fact #4: This has been covered in our FAQ from the beginning.

John Hopkins cryptographer professor Matthew Green says that Mega's claims of a Javascript verification system "make no sense." ... "If the Javascript is verifying itself, it's like trying to pick yourself up by our bootstraps, which doesn't work," says Green. "You need something trusted on the user's machine to check the Javascript, and they don't have that."

Please do not rely on hearsay, even if you are a cryptographer professor. Instead, go to the actual site and look at the actual code. Fact #1: The JavaScript is not verifying itself. Fact #2: A piece of JavaScript coming from a trusted, 2048-bit HTTPS server is verifying additional pieces of JavaScript coming from untrusted, HTTP/1024-bit HTTPS servers. This basically enables us to host the extremely integrity-sensitive static content on a large number of geographically diverse servers without worrying about security.
MegaCracker An excellent reminder not to use guessable/dictionary passwords, specifically not if your password also serves as the master encryption key to all files that you store on MEGA.

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.

Sunday, January 20, 2013

''No one shall be subjected to arbitrary interference with his privacy, family, home or correspondence. Everyone has the right to the protection of the law against such interference.'' - Human Rights Declaration



In less than 10 minutes, you can drastically improve your privacy online and protect yourself against unwanted and invisible tracking.
Note that these privacy safeguards will also be blocking some ads. EFF is working with online advertisers to try to convince them to provide real privacy protections for users, but until they agree to meaningful standards about online tracking, these steps will be necessary for users to safeguard their browsing privacy. Aside from removing ads, these changes won't affect your browsing experience on the vast majority of websites. It's possible, however, that a tiny fraction of websites may behave differently or break, in which case the easiest solution is to temporarily use a "private browsing" mode without the settings enabled, or a fresh browser profile/user with default settings.
Firefox instructions Chrome instructions

Step 1: Install Adblock Plus

Get Adblock Plus. After it is installed, be sure to change your filter preferences to add EasyPrivacy:
Then go to "Add Filter Subscription" -> "Add a different subscription" and select "EasyPrivacy":

Step 2: Change Cookie Settings

Now you are going to set your cookies to expire when you exit your browser, and disallow third-party cookies from being set. To do this, go to Edit -> Preferences -> Privacy. Under "History", choose the drop down "Use custom settings for history". Under "Accept cookies from sites", uncheck "Accept third-party cookies", and right below select "Keep until I close Firefox":
Great! No more unwanted tracking cookies.

Step 3: Turn Off Referers

This famously misspelled header typically sent by default with every HTTP request gives a lot of potentially personal information to websites. But you can turn it off. Open a new tab and in your URL bar, type "about:config". You will see a scary warning; click "I'll be careful, I promise!" At the search bar, type "referer". You should see the value "network.http.sendRefererHeader". Double click it, and change the value to 0:
Ta da! No more referers. Now close that tab if you are worried about accidentally changing other settings.

Step 4: Install HTTPS Everywhere

Install EFF's browser add-on HTTPS Everywhere. This maximizes your use of HTTPS to ensure that your private conversations with websites can't be snooped on or tampered with by other parties.
Congratulations! You are now in an elite group of users fighting back against unwanted privacy invasions. Give yourself a pat on the back, and then please share these tips.

Step 1: Install Adblock Plus

Get Adblock Plus. After it is installed, be sure to change your filter preferences to add EasyPrivacy. To do this, first visit the AdBlock Plus website. Click on the link to "Add EasyPrivacy to Adblock Plus":
This should take you to the Adblock Plus options screen. Simply click add and you're all set:

Step 2: Change Cookie Settings

Now you are going to set your cookies to expire when you exit your browser, and disallow third-party cookies from being set. To do this, locate the Chrome settings menu, which should one of the following two icons in the top right of your browser:
or
From this menu, go to "Settings", and scroll to the bottom and click "Show Advanced Settings." Under "Privacy", click "Content Settings". Select "Keep local data only until I quit my browser / for current session", and check "Block third-party cookies and site data":
Great! No more unwanted tracking cookies.

Step 3: Turn Off Referers

This famously misspelled header typically sent by default with every HTTP request gives a lot of potentially personal information to websites. But you can turn it off. To do so, install the extension Referer Control . After installing, scroll down and locate the text "default referer for all other sites" and click "Block":
Ta da! No more referers.

Step 4: Install HTTPS Everywhere

Install EFF's browser add-on HTTPS Everywhere. This maximizes your use of HTTPS to ensure that your private conversations with websites can't be snooped on or tampered with by other parties.
Congratulations! You are now in an elite group of users fighting back against unwanted privacy invasions. Give yourself a pat on the back, and then please share these tips.

And One More Thing: Install Ghostery 

Related Posts Plugin for WordPress, Blogger...