Hollywood's New War on Software Freedom and Internet Innovation

This is the third in our series (Part 1, Part 2) breaking down the potential effects of the Stop Online Piracy Act (SOPA), an outrageous and grievously misguided bill now working its way through the House of Representatives. This post discusses dangerous software censorship provisions that are new in this bill, as well as the DNS censorship provisions it inherited from the Senate's COICA and PIPA bills. Please help us fight this misguided legislation by contacting Congress today.

In this new bill, Hollywood has expanded its censorship ambitions. No longer content to just blacklist entries in the Domain Name System, this version targets software developers and distributors as well. It allows the Attorney General (doing Hollywood or trademark holders' bidding) to go after more or less anyone who provides or offers a product or service that could be used to get around DNS blacklisting orders. This language is clearly aimed at Mozilla, which took a principled stand in refusing to assist the Department of Homeland Security's efforts to censor the domain name system, but we are also concerned that it could affect the open source community, internet innovation, and software freedom more broadly:

• Do you write or distribute VPN, proxy, privacy or anonymization software? You might have to build in a censorship mechanism — or find yourself in a legal fight with the United States Attorney General.
• Even some of the most fundamental and widely used Internet security software, such as SSH, includes built-in proxy functionality. This kind of software is installed on hundreds of millions of computers, and is an indispensable tool for systems administration professionals, but it could easily become a target for censorship orders under the new bill.
• Do you work with or distribute zone files for gTLDs? Want to keep them accurate?  Too bad — Hollywood might argue that if you provide a complete (i.e., uncensored) list, you are illegally helping people bypass SOPA orders. 
• Want to write a client-side DNSSEC resolver that uses multiple servers until it finds a valid signed entry? Again, you could be in a fight with the U.S. Attorney General.

via eff.org