ellipsix informatics
2012
Apr
23

A close look at CISPA

You may remember that about three months ago, the internet erupted in an uproar over two copyright protection bills, SOPA and PIPA, which were working their way through the House of Representatives and the Senate, respectively. Now there is another bill, the Cyber Intelligence Sharing and Protection Act (CISPA), which has many of the same people concerned. Indeed, a lot of privacy advocates are warning that CISPA is even worse than SOPA and PIPA. But other people are saying that it's nowhere near as bad. One way or another, there seems to be a lot of misinformation floating around about this bill, so just as I did with PIPA, I thought it would be useful to go straight to the source and see what CISPA is really about.

As usual, this post comes with the standard disclaimer that I am not a lawyer and this is not legal advice. I make no guarantees about the correctness of this information. If you're concerned about specific effects that CISPA could have on you personally, check with a lawyer.

Now then, to the source. The text of the bill itself can be found on the Library of Congress website as House Resolution 3523. It consists of an addition to title 50 of the United States Code, which deals with national security. The proposed addition starts out as follows:

Sec. 1104. (a) Intelligence Community Sharing of Cyber Threat Intelligence With Private Sector--

(1) IN GENERAL- The Director of National Intelligence shall establish procedures to allow elements of the intelligence community to share cyber threat intelligence with private-sector entities and to encourage the sharing of such intelligence.

This basically sums up a large part of what people consider to be the problem with CISPA. It allows the government, or more precisely the national intelligence community (FBI, CIA, NSA, and other such organizations) to share information they have collected with private-sector entities, like businesses. Now, I don't know exactly what information our intelligence agencies collect on U.S. residents, but it stands to reason that if they wanted it, they could have access to phone records and the content of phone calls, emails, personal information like your address history and phone number history, your employment history and credit history, all your financial information, most of your shopping preferences, large parts of your web browsing history, and assorted other information. Obviously, government agencies can get far more information on your life and habits than private businesses or random people can. If a channel is opened up by which businesses can get a share of that information, they'd have a field day — and who knows what kinds of nefarious tricks they could pull with it?

But let's hold on a minute. The capacity for information sharing that CISPA introduces comes with restrictions, which are spelled out by the next paragraph of the bill.

(2) SHARING AND USE OF CLASSIFIED INTELLIGENCE- The procedures established under paragraph (1) shall provide that classified cyber threat intelligence may only be--

(A) shared by an element of the intelligence community with--

(i) certified entities; or

(ii) a person with an appropriate security clearance to receive such cyber threat intelligence;

(B) shared consistent with the need to protect the national security of the United States; and

(C) used by a certified entity in a manner which protects such cyber threat intelligence from unauthorized disclosure.

A "certified entity" is defined in subsection (g) of the bill as follows:

(1) CERTIFIED ENTITY- The term `certified entity' means a protected entity, self-protected entity, or cybersecurity provider that--

(A) possesses or is eligible to obtain a security clearance, as determined by the Director of National Intelligence; and

(B) is able to demonstrate to the Director of National Intelligence that such provider or such entity can appropriately protect classified cyber threat intelligence.

and in turn, "protected entity," "self-protected entity," and "cybersecurity provider," and the related term "cybersecurity purpose," are defined as

(4) CYBERSECURITY PROVIDER- The term `cybersecurity provider' means a non-governmental entity that provides goods or services intended to be used for cybersecurity purposes.

(5) CYBERSECURITY PURPOSE- The term `cybersecurity purpose' means the purpose of ensuring the integrity, confidentiality, or availability of, or safeguarding, a system or network, including protecting a system or network from--

(A) efforts to degrade, disrupt, or destroy such system or network; or

(B) theft or misappropriation of private or government information, intellectual property, or personally identifiable information.

(7) PROTECTED ENTITY- The term `protected entity' means an entity, other than an individual, that contracts with a cybersecurity provider for goods or services to be used for cybersecurity purposes.

(8) SELF-PROTECTED ENTITY- The term `self-protected entity' means an entity, other than an individual, that provides goods or services for cybersecurity purposes to itself.'

OK, soo... if I'm getting this right, certified entities are basically businesses or organizations that either produce or use (or both) computer security technology, and either have or are eligible for a certain level of security clearance, and which confirm that they are capable of protecting whatever information they receive from unauthorized use. Sure, simply being capable of obtaining a security clearance, and being capable of protecting information, is not saying much. That's where subparagraph (C) comes in; it actually requires these certified entities to protect the information they're given. In essence, the bill is setting up the framework to ensure that, once privileged information leaves the intelligence community, it doesn't go any further.

Now, what sort of information gets out in the first place? That is loosely addressed by subparagraph (B), which says that the government can only share information as necessary to protect national security. There are a couple of problems I have with this statement, though. First of all, it's really vague on what exactly is necessary to protect national security. I understand that intelligence services need to have flexible tools to deal with problems that they haven't anticipated, and it would hinder their work to specify a complete list of circumstances under which information could be shared outside the government, but I really feel like some restrictions could be put in place here — for example, sharing information might only be allowed

  1. when necessary to get access to additional information for which the private entity is the only source, or
  2. when necessary to facilitate the cooperation of the private entity in an ongoing investigation; and
  3. in the face of an imminent threat to national security such that the delay required to go through legal proceedings in a court (i.e. getting a warrant) could lead to property damage or loss of life.

It might be necessary to create some additional procedure by which a court could approve a request to share information with the private sector, since warrants are usually used to take things, not to give them out (as far as I know), but certainly that could be part of the bill as well. Honestly, I'm not sure exactly what sorts of situations prompted this bill to be written, and so I'm not sure what sorts of restrictions would be appropriate. But if history is any indication, intelligence agencies will try pretty hard to pass all sorts of things off as being required in the name of national security, and the current wording gives them free reign to do just that. And as with any organization, there are almost certainly going to be a few people in the intelligence community who would abuse that power.

The other thing that bothers me about this is that there is no accountability for what information gets shared and why it had to be shared. Later on in the bill, subsection (d) specifically, there is a provision that specifies that any sharing of information with the federal government under this act must be described in an annual report to Congress. But it says nothing about information shared by the federal government.

(d) Report on Information Sharing--

(1) REPORT- The Inspector General of the Intelligence Community shall annually submit to the congressional intelligence committees a report containing a review of the use of information shared with the Federal Government under this section, including--

(A) a review of the use by the Federal Government of such information for a purpose other than a cybersecurity purpose;

(B) a review of the type of information shared with the Federal Government under this section;

(C) a review of the actions taken by the Federal Government based on such information;

(D) appropriate metrics to determine the impact of the sharing of such information with the Federal Government on privacy and civil liberties, if any; and

(E) any recommendations of the Inspector General for improvements or modifications to the authorities under this section.

(2) FORM- Each report required under paragraph (1) shall be submitted in unclassified form, but may include a classified annex.

I for one would feel much better knowing that if somebody is abusing the ability to share classified information, there is at least a framework set up for that to be reported to a higher authority. (Not that I really trust Congress, but like it or not, it is their job to oversee intelligence activities.)

Whew. OK. Let's move on to the next part of the bill, subsections (b) and (c), which deal with the reverse process, namely when private-sector entities share information with federal intelligence services.

(b) Private Sector Use of Cybersecurity Systems and Sharing of Cyber Threat Information-

(1) IN GENERAL-

(A) CYBERSECURITY PROVIDERS- Notwithstanding any other provision of law, a cybersecurity provider, with the express consent of a protected entity for which such cybersecurity provider is providing goods or services for cybersecurity purposes, may, for cybersecurity purposes--

(i) use cybersecurity systems to identify and obtain cyber threat information to protect the rights and property of such protected entity; and

(ii) share such cyber threat information with any other entity designated by such protected entity, including, if specifically designated, the Federal Government.

(B) SELF-PROTECTED ENTITIES- Notwithstanding any other provision of law, a self-protected entity may, for cybersecurity purposes--

(i) use cybersecurity systems to identify and obtain cyber threat information to protect the rights and property of such self-protected entity; and

(ii) share such cyber threat information with any other entity, including the Federal Government.

This part seems straightforward enough; it's basically saying that a technology security company can share with the government (or anyone else) information about threats to its systems or its clients' resources, with the explicit permission of the client, when doing so is necessary for the company to do its job of protecting the client.

(2) USE AND PROTECTION OF INFORMATION- Cyber threat information shared in accordance with paragraph (1)--

(A) shall only be shared in accordance with any restrictions placed on the sharing of such information by the protected entity or self-protected entity authorizing such sharing, including appropriate anonymization or minimization of such information;

(B) may not be used by an entity to gain an unfair competitive advantage to the detriment of the protected entity or the self-protected entity authorizing the sharing of information; and

(C) if shared with the Federal Government--

(i) shall be exempt from disclosure under section 552 of title 5, United States Code;

(ii) shall be considered proprietary information and shall not be disclosed to an entity outside of the Federal Government except as authorized by the entity sharing such information; and

(iii) shall not be used by the Federal Government for regulatory purposes.

And this part specifies conditions on when and how that information can be shared: basically that it has to be done in accordance with the company's own privacy policy, and that it can't be used for inappropriate purposes (though I'm not positive that "can't be used for competitive advantage" really covers all the inappropriate purposes one could come up with). It also says that information shared with the government is exempt from Freedom of Information Act requests, which is a pretty necessary stipulation, so it's good to see that that was included.

(3) EXEMPTION FROM LIABILITY- No civil or criminal cause of action shall lie or be maintained in Federal or State court against a protected entity, self-protected entity, cybersecurity provider, or an officer, employee, or agent of a protected entity, self-protected entity, or cybersecurity provider, acting in good faith--

(A) for using cybersecurity systems or sharing information in accordance with this section; or

(B) for not acting on information obtained or shared in accordance with this section.

This paragraph is an interesting inclusion mostly because of the second item, which provides immunity from prosecution for declining to use any of this cybersecurity information. I like this clause because it means that, if you're ever not sure about the legal status of some information shared pursuant to this act, the safe "default" course of action is to just leave it alone, and that way there will be no legal consequences. This is much better than the alternative of providing immunity from prosecution for people who believed they were acting in compliance with CISPA but who actually weren't.

There is one thing I don't get about this subsection, though. Why is it even necessary? After all, most companies already have privacy policies, and most of those already say that they may share information with the government in accordance with a court order or when necessary to protect their business, in some cases even without explicit approval by the client. Now, granted, this is coming from the perspective of an individual, and subsection (b) does not apply to individuals (it talks about "protected entities," which are organizations, not people). But I would imagine that businesses have similar agreements in place when they deal with each other. So everything that this piece of CISPA allows was already perfectly legal? Maybe it just needed to be explicit, but I just don't see the point.

There's one more piece of the bill that I want to look at, and that is subsection (c), which governs how the federal government (in particular, the intelligence community) may use any information it receives from private-sector entities.

(c) Federal Government Use of Information-

(1) LIMITATION- The Federal Government may use cyber threat information shared with the Federal Government in accordance with subsection (b) for any lawful purpose only if--

(A) the use of such information is not for a regulatory purpose; and

(B) at least one significant purpose of the use of such information is--

(i) a cybersecurity purpose; or

(ii) the protection of the national security of the United States.

OK, so they can't use it to influence policymaking, or at least that's what I assume "not for a regulatory purpose" is supposed to mean. But would it be so hard to just prohibit using this information for any purpose other than protecting national security? I feel like that would be a lot cleaner, and it closes the loophole of someone thinking up a wacky way to use shared information that is not regulatory but not intelligence-related either.

(3) ANTI-TASKING RESTRICTION- Nothing in this section shall be construed to permit the Federal Government to--

(A) require a private-sector entity to share information with the Federal Government; or

(B) condition the sharing of cyber threat intelligence with a private-sector entity on the provision of cyber threat information to the Federal Government.

This final piece (that I'm going to talk about) says that the bill does not give the government the authority to demand information from a private company, at least not in any way that isn't already permitted by existing laws (namely, with a search warrant). It's definitely a good thing to make clear that intelligence agencies are still not allowed to bypass the judicial process; CISPA does not enable warrantless wiretapping and the like.

So where does that leave us? Well, there are a lot of people saying CISPA is worse than SOPA and PIPA. I do not agree. The thing that particularly bothered me about the PROTECT-IP Act was that it allowed the government to take highly restrictive actions against website operators without going through the judicial process to determine whether those website operators had actually done anything wrong. It tinkered with the "innocent until proven guilty" mantra that our justice system is (supposed to be) based on. CISPA does not. In fact, as I pointed out above, there are a couple of clauses inserted which effectively prevent the intelligence community from escaping judicial oversight (any more than they already do).

On the other hand, CISPA does enable some channels for information sharing which, in my opinion, are not sufficiently regulated and monitored. If Wikipedia is to be believed, the bill's sponsors are considering another round of changes that may help close some of the loopholes I've identified, but that's still tentative; besides, if you're the type of person who is a little more concerned about privacy than I am, then the idea of this information sharing in any form probably seems pretty bad. I'll probably be contacting my representatives about this, and whatever your opinion about it, I encourage you to do the same!

2012
Jan
19

Senator Ron Wyden gets it

Ron Wyden, senator from Oregon, released a very insightful letter yesterday in support of the SOPA blackout.

Protect IP (PIPA) and the Stop Online Piracy Act (SOPA) are a step towards a different kind of Internet. They are a step towards an Internet in which those with money and lawyers and access to power have a greater voice than those who don’t. They are a step towards an Internet in which online innovators need lawyers as much or more than they need good ideas. And they are a step towards a world in which Americans have less of a voice to argue for a free and open Internet around the world.

See the full letter on Sen. Wyden's site.

2012
Jan
18

PROTECT-IP: the source

Yesterday, I made a post about the PROTECT-IP Act, explaining in some detail why it's such a dangerous proposition. But if you're like me, maybe you're tired of hearing second-hand arguments. You're not scared of a little legalese, and you want to check out the original source, Senate resolution 968 itself. Well, great! That's what this blog is really (or at least tries to be) about, and that's what I'm going to do in this post.

I have two goals here. For one thing, I'm trying to correct some of the misinformation that may be floating around on the web about PIPA. But I also want to make the point that laws aren't as scary as you might think. When you take a good, close look at them, it's not that hard to understand what is being said — sure, not well enough to argue them in court (unless you're a lawyer), but you can get a pretty decent sense of what is and isn't allowed.

This comes with two standard disclaimers:

  1. I am strongly opposed to PIPA (and SOPA). This post is an attempt to convince others to share that view. But it's more of a justification of my opinion than a rant about it. I've tried to include enough direct quotes to make it clear why I oppose this bill, and to hopefully allow you to come to the same conclusion; I'm not saying you should agree with me just because I say so. The point: keep an open mind, and whatever opinion you have, make sure you know why you have it.
  2. I am not a lawyer and this is not legal advice. I make no guarantees about the correctness of this information. If you're concerned about specific effects that PIPA or SOPA could have on you personally, check with a lawyer.

Definition of Copyright Infringement

PIPA, for all the fuss people have been saying about it, really just builds on existing copyright laws. So it makes sense to start by examining those laws, which are contained in title 17 of the United States Code.

Title 17 is a very long document, but there are three short parts that are especially relevant for interpreting PIPA. First, section 106 (or in the standard notation, 17 U.S.C. §106) defines six rights that are reserved to the holder of a copyright:

Subject to sections 107 through 122, the owner of copyright under this title has the exclusive rights to do and to authorize any of the following:

(1) to reproduce the copyrighted work in copies or phonorecords;

(2) to prepare derivative works based upon the copyrighted work;

(3) to distribute copies or phonorecords of the copyrighted work to the public by sale or other transfer of ownership, or by rental, lease, or lending;

(4) in the case of literary, musical, dramatic, and choreographic works, pantomimes, and motion pictures and other audiovisual works, to perform the copyrighted work publicly;

(5) in the case of literary, musical, dramatic, and choreographic works, pantomimes, and pictorial, graphic, or sculptural works, including the individual images of a motion picture or other audiovisual work, to display the copyrighted work publicly; and

(6) in the case of sound recordings, to perform the copyrighted work publicly by means of a digital audio transmission.

In short: copying, modification, distribution, public performance or display, and broadcasting all require the copyright holder's consent. If you do any of these things without having permission from the copyright holder, this is defined by section 501 as copyright infringement.

(a) Anyone who violates any of the exclusive rights of the copyright owner as provided by sections 106 through 122 or of the author as provided in section 106A (a), or who imports copies or phonorecords into the United States in violation of section 602, is an infringer of the copyright or right of the author, as the case may be.

In addition to the six actions mentioned above, it's also illegal to provide specific information that allows someone else to bypass technological measures which prevent them from infringing copyright. For example, the contents of DVDs are encrypted, and distributing the software that allows people to break the encryption and use the DVD is illegal — unless you have permission from whoever owns the copyright on the DVD contents. Section 1201 has the details. It's kind of long, but here are some of the important parts:

(a) Violations Regarding Circumvention of Technological Measures.

(1)

(A) No person shall circumvent a technological measure that effectively controls access to a work protected under this title....

....

(2) No person shall manufacture, import, offer to the public, provide, or otherwise traffic in any technology, product, service, device, component, or part thereof, that—

(A) is primarily designed or produced for the purpose of circumventing a technological measure that effectively controls access to a work protected under this title;

(B) has only limited commercially significant purpose or use other than to circumvent a technological measure that effectively controls access to a work protected under this title; or

(C) is marketed by that person or another acting in concert with that person with that person’s knowledge for use in circumventing a technological measure that effectively controls access to a work protected under this title.

and so on. (If you're about to complain that I'm taking this out of context, great! Go read it yourself.)

The laws I've listed above, sections 501 and 1201, are referenced by the PROTECT-IP Act in its definition of "internet site dedicated to infringing activities." The following text occurs in section 2 of the bill:

(7) the term 'Internet site dedicated to infringing activities' means an Internet site that--

(A) has no significant use other than engaging in, enabling, or facilitating the--

(i) reproduction, distribution, or public performance of copyrighted works, in complete or substantially complete form, in a manner that constitutes copyright infringement under section 501 of title 17, United States Code;

(ii) violation of section 1201 of title 17, United States Code; or

(iii) sale, distribution, or promotion of goods, services, or materials bearing a counterfeit mark, as that term is defined in section 34(d) of the Lanham Act; or

(B) is designed, operated, or marketed by its operator or persons operating in concert with the operator, and facts or circumstances suggest is used, primarily as a means for engaging in, enabling, or facilitating the activities described under clauses (i), (ii), or (iii) of subparagraph (A);

This definition winds up being the legal basis for the enforcement procedures in later sections of the bill. In other words, if you get sued or prosecuted under PIPA, it will be because you allegedly violated one of these existing laws, 17 U.S.C. §501 or §1201. This is why, in my previous post, I wrote that PIPA doesn't add anything new to copyright infringement — for ordinary citizens, it doesn't make anything illegal that wasn't already illegal. It does require certain behaviors from ISPs, DNS providers, payment gateways, and advertisers, but we'll get to that later.

Legal Responses to Infringing Content

What PIPA does do is drastically increase the allowable penalties for having copyrighted material hosted on your site. This is one of the parts that many people find particularly objectionable about it (and SOPA).

DMCA Safe Harbor Provision

At issue is the fact that a lot of websites these days get much of their content from contributions by their users. And it's possible that some of those contributions are infringing material. Under the direct interpretation of 17 U.S.C. §501, the website hosting the content is legally liable for this, because by hosting the content and allowing others to download it, they are either distributing it or publicly displaying it, perhaps depending on how technically-minded you are.

Currently, the law that governs the consequences of online copyright infringement is the Digital Millennium Copyright Act. It's gotten its fair share of complaints, but it's nowhere near as restrictive as SOPA and PIPA. One of the main reasons the DMCA has been considered tolerable is codified in 17 U.S.C. §512, of which an excerpt follows:

(c) Information Residing on Systems or Networks At Direction of Users.—

(1) In general.— A service provider shall not be liable for monetary relief, or, except as provided in subsection (j), for injunctive or other equitable relief, for infringement of copyright by reason of the storage at the direction of a user of material that resides on a system or network controlled or operated by or for the service provider, if the service provider—

(A)

(i) does not have actual knowledge that the material or an activity using the material on the system or network is infringing;

(ii) in the absence of such actual knowledge, is not aware of facts or circumstances from which infringing activity is apparent; or

(iii) upon obtaining such knowledge or awareness, acts expeditiously to remove, or disable access to, the material;

(B) does not receive a financial benefit directly attributable to the infringing activity, in a case in which the service provider has the right and ability to control such activity; and

(C) upon notification of claimed infringement as described in paragraph (3), responds expeditiously to remove, or disable access to, the material that is claimed to be infringing or to be the subject of infringing activity.

This snippet is part of what is known as the Online Copyright Infringement Liability Limitation Act, at least according to Wikipedia. Most people just call it the safe harbor provision. Essentially, it means that if you're operating an online service on which somebody has uploaded material that infringes copyright, you're not legally liable for the infringement, as long as you take the material offline upon receiving a proper notice. This puts the primary responsibility for avoiding copyright infringement on the users who upload it, not on the host. It allows sites like Facebook, Wikipedia, and Reddit (and millions of others) to exist without having to actively monitor the material uploaded by their users for copyright violations.

PROTECT-IP

Under PIPA, it's a whole different story. This bill doesn't contain anything analogous to the DMCA safe harbor provision. What it does contain is the following piece, in section 3, which allows the U.S. Attorney General to obtain a court order calling for legal action against a foreign site (more on this later) suspected of copyright infringement.

(1) IN GENERAL- On application of the Attorney General following the commencement of an action under this section, the court may issue a temporary restraining order, a preliminary injunction, or an injunction, in accordance with rule 65 of the Federal Rules of Civil Procedure, against the nondomestic domain name used by an Internet site dedicated to infringing activities, or against a registrant of such domain name, or the owner or operator of such Internet site dedicated to infringing activities, to cease and desist from undertaking any further activity as an Internet site dedicated to infringing activities, if--

(A) the domain name is used within the United States to access such Internet site; and

(B) the Internet site--

(i) conducts business directed to residents of the United States; and

(ii) harms holders of United States intellectual property rights.

Note that all of the following measures can be imposed based on only a court order. Not a full trial. All that is needed is for a judge to sign off on it.

Later on in the section, PIPA specifies the actions that can be taken against alleged copyright infringers:

(d) Required Actions Based on Court Orders-

(2) REASONABLE MEASURES- After being served with a copy of an order pursuant to this subsection:

(A) OPERATORS-

(i) IN GENERAL- An operator of a nonauthoritative domain name system server shall take the least burdensome technically feasible and reasonable measures designed to prevent the domain name described in the order from resolving to that domain name's Internet protocol address....

This requires operators of DNS nameservers to remove all DNS records of the infringing domain, so the site can't be accessed by name. For example, if the DNS records for this site were removed, www.ellipsix.net would no longer resolve to my server's IP address, 69.164.216.133, and you would have to know those numbers in order to access this site. If the nameservers that hold these records are not under U.S. jurisdiction, ISPs would be required to present "fake" DNS records which lead you to the wrong website when you type the domain name into your browser. This would be a Bad Thing because the way DNS works, servers all over the world have to sync up with each other, and trust that they are in sync. PIPA's DNS provisions would break that, and instead require that U.S.-based DNS servers provide different information from foreign servers, which could potentially wreak havoc on the system. Besides, in practice, it's pretty easy to register another domain name for any given site, which makes this particular countermeasure fairly ineffective.

(B) FINANCIAL TRANSACTION PROVIDERS- A financial transaction provider shall take reasonable measures, as expeditiously as reasonable, designed to prevent, prohibit, or suspend its service from completing payment transactions involving customers located within the United States and the Internet site associated with the domain name set forth in the order.

This prohibits banks and other financial institutions (like PayPal) from brokering transactions between anyone in the United States and the infringing site. If this provision were invoked on an online business, it would completely shut down their ability to operate within the U.S. Or, applied to a nonprofit foundation, it cuts off their ability to receive donations from Americans.

(C) INTERNET ADVERTISING SERVICES- An Internet advertising service that contracts with the Internet site associated with the domain name set forth in the order to provide advertising to or for that site, or which knowingly serves advertising to or for such site, shall take technically feasible and reasonable measures, as expeditiously as reasonable, designed to--

(i) prevent its service from providing advertisements to the Internet site associated with such domain name; or

(ii) cease making available advertisements for that site, or paid or sponsored search results, links or other placements that provide access to the domain name.

This subparagraph prohibits online advertising agencies from displaying ads on the infringing site, and from displaying ads for the infringing site. Like the previous item, this would drastically limit an online business's ability to reach out to potential customers, and it also prevents sites of all sorts from gaining revenue by displaying ads. This is a reasonable tactic to take against websites that truly are devoted to infringing activities, because advertisements are often how they make their money. But without the proper procedures to ensure that it doesn't get misused, it's a dangerous provision.

(D) INFORMATION LOCATION TOOLS- An service provider of an information location tool shall take technically feasible and reasonable measures, as expeditiously as possible, to--

(i) remove or disable access to the Internet site associated with the domain name set forth in the order; or

(ii) not serve a hypertext link to such Internet site.

This last subparagraph requires search engines and similar sites, potentially including anything that links to other sites (i.e. any website in existence) to remove from their listings any results for the infringing site. Outside of China, most (useful) content on the web is found through U.S.-based search engines, specifically Google, Bing, and Yahoo. Forcibly removing a site from all their results will flat-out kill it.

Of course, as with the advertising clause, if a true copyright infringement site gets hit with this, then good, the law is working. But in a case of mistaken identity, overzealous prosecution, or judicial corruption (rare, but it happens), if a non-infringing site like Wikipedia is removed from search engine results, the consequences will be pretty disastrous. Just think, what would it be like if today's Wikipedia blackout were permanent, and you couldn't get around it by hitting Esc at the right time?

There are similar provisions in section 4 which allow the copyright holder (in addition to the Attorney General) to take similar actions. But there are a couple of key differences:

  • Section 4 applies to domestic sites, or rather domestic domain names, whereas section 3 applies to foreign domain names.
  • Section 4 only compels financial institutions and advertising networks to cut ties with the site. It doesn't say anything about DNS or search engines.

Still, that's a pretty heavy hammer to hit a site with. It may not take them entirely offline, at least not directly, but it does cut off the site's financial support, and any website that's reasonably popular needs that financial support to survive.

Proactive Takedowns

In sections 3 and 4, PIPA specifies that the U.S. Attorney General or a copyright holder can initiate legal action against a website they allege to be infringing copyright. But that's not the end of it. Section 5(a) goes beyond that and actually encourages financial institutions and advertising services to proactively cut off websites for suspected copyright violations by providing them with legal immunity for doing so.

(a) In General- No financial transaction provider or Internet advertising service shall be liable for damages to any person for voluntarily taking any action described in section 3(d) or 4(d) with regard to an Internet site if the entity acting in good faith and based on credible evidence has a reasonable belief that the Internet site is an Internet site dedicated to infringing activities.

In other words, as long as they act with a "reasonable belief" that the website is "dedicated to infringing activities", the financial institution or ad provider suffers no legal consequences for terminating their relationship with the site, regardless of whether the alleged copyright infringement turns out to be valid or not. There are a couple of problems with this: first of all, it encourages what is effectively virtual vigilante justice, in which websites are subject to disciplinary action, with legal force, but without going through the full process of the American justice system. But perhaps more worrying is the fact that "reasonable belief" can be twisted to mean all sorts of things. Admittedly I can understand Congress's motivation to give companies some flexibility to stamp out online copyright infringement — but when you have the ability to completely "bury" a website, that ability needs to be strictly controlled.

Applicability

PIPA uses the phrase "nondomestic domain name" in several places, especially in section 3, which (if you remember) specifies the actions that the Attorney General can bring against foreign sites with a court order. Some supporters of the bill argue that this provision prevents it from being used against, for lack of a better term, "good" websites — the ones that are obviously not copyright infringers, and are just trying to make the internet a better place.

But there's a problem with that. Look at the definition in section 2:

(9) the term 'nondomestic domain name' means a domain name for which the domain name registry that issued the domain name and operates the relevant top level domain, and the domain name registrar for the domain name, are not located in the United States;

The internet is a global network, where boundaries between different countries often get blurred. It's not at all uncommon that a website uses a domain name from one country, a registrar in a different country, and a hosting service in yet another country. For example, a lot of major websites operate URL shorteners whose domain names, like bit.ly, are registered with foreign registrars to take advantage of various two-letter country codes. All of those qualify as nondomestic for purposes of PIPA. On the other hand, a website registered with a U.S. domain name won't necessarily operate in the U.S. In particular, the major top-level domains like .com and .net are operated by American registrars. Many sites thus qualify as domestic under PIPA even though the U.S. government ostensibly no jurisdiction over them.

Besides all that, the fact is that many internet companies have multinational operations. Domain name registrars can have servers in many different countries, and can distribute their operations among these servers in various ways, which potentially allows the domains they host to be considered either domestic or nondomestic depending on when a court order is issued against them. Many larger websites themselves have operations in multiple countries — they may host files on content delivery networks which have servers around the world, and they may hold multiple domain names registered in different countries. Example: Google holds google.com, google.ca, google.co.uk, and a whole bunch of others. All of this makes it pretty murky to determine whether any given website is actually considered domestic or nondomestic, and there's no guarantee that the answer you get will really make sense.

Conclusions

So what are we going to do about all this? If you agree that these bills would be dangerous for the internet, contact your senators and representatives and ask them to vote against SOPA (H.R. 3261) and PROTECT-IP (S. 968)! Information on how to do that is all over the web, especially on several of the major websites which are blacked out today:

  • Wikipedia will show you contact information for your representatives based on your ZIP code
  • Google lets you add your name to a petition that will demonstrate the level of nationwide opposition to the bills
  • Reddit is a continuing source of information (decidedly in opposition) on both bills
  • American Censorship maintains a contact form for your representatives in Congress
  • The full text of each bill can always be accessed through the Library of Congress:

  • You can also have a look at some other posts I've written about these bills

  • Finally, get out and spread the word among your friends!
2012
Jan
17

Why is PROTECT-IP so bad?

As I recently posted, SOPA and PIPA, the bills that represent the next step in the media industries' war on piracy (or, to be fair, what they call piracy), have been getting increasing amounts of attention. And it's bringing results: just yesterday, the Stop Online Piracy Act (SOPA) was pulled from consideration in the House of Representatives.

While this is a big win for the internet, it's only part of the battle, because the PROTECT-IP Act (PIPA), a nearly identical bill, is still scheduled for a vote in the Senate on January 24, a week from today. So it's still not too late to contact your senators and ask them to oppose the bill! Wikipedia has also joined the cause, pledging to black out its site tomorrow to raise awareness.

The Problem with PIPA

A friend of mine recently made a post about SOPA on the FreshySites blog which I think shows how some of the information about what these bills do has been distorted as it's traveled around the web. With the blackouts of Wikipedia, Reddit, and other sites poised to draw a lot of public attention to the bills, I thought this would be an opportune time to clarify exactly why PIPA is so bad.

Contrary to what some people are saying, PIPA does not actually change the definition of copyright infringement. It doesn't make anything illegal that wasn't illegal before (except for certain companies, but more on that later). What it does do is drastically increase the penalties you face if you are infringing copyright. Currently, under the DMCA, if someone asserts that copyrighted material is available on your site, you can take the material off the site. As long as you do this promptly upon receiving the proper sort of request, you're not responsible for the copyright infringement. If the person who originally posted it doesn't believe that the copyright violation is really a violation at all, they can file a counter-notice to say so; then it goes to court, and the copyright holder has to prove that the copyright violation is real.

Under PIPA, that whole procedure changes. If someone asserts that copyrighted material is available on your site, according to subsections 3(d) and 4(d) of PIPA, they can get a court order requiring the following

  • Payment services, like PayPal and credit card companies, are forbidden from doing business with you.
  • Advertising agencies are forbidden from placing ads on your site.

Additionally, if your site is “foreign” (you’re using a web host or DNS registrar in another country):

  • Your domain name gets removed from American DNS resolvers.
  • American search engines are no longer allowed to list your site.

Even though the restrictions only apply to companies that operate in the US, that still cuts you off from Google, Bing, Yahoo, PayPal, Visa, MasterCard, and most banks, not to mention your whole site is inaccessible from anywhere in America — all based on the accusation that you were hosting copyright material. Even if it wasn’t under your control (say, one of your site's users uploaded it), you still suffer the consequences.

The other thing to complain about is that in section 5, PIPA encourages websites, ISPs, DNS resolvers, search engines, etc. to proactively blacklist sites that they suspect might be in violation of the act. So, for example, Google can remove your website from their search listings, or PayPal can arbitrarily close your account, or so on, and as long as they claim a reasonable belief (whatever that means) that your site was infringing copyrights, you have no recourse against them. To some extent, this is already possible, since most of these sites’ terms of service include a provision that they may terminate your account for any or no reason. But those provisions don't have the legal force of the US Justice Department behind them. Right now, Google isn't required to remove a site from their search index just because the government says the site is violating copyright. PIPA would change that. Hopefully, you can see how this opens up a huge potential for abuse.

2012
Jan
15

Update on the fight against SOPA and PIPA

I've written a couple of posts about SOPA and PIPA, the copyright legislation currently making its way through Congress, and the widespread efforts to stop it. There's some good news on that front: these pieces of legislation have been attracting increasing amounts of media attention lately, and Congress is beginning to respond. The DNS blocking provisions of the bill have been pulled (for now, at least), removing a threat to one of the foundations of the internet, and over in the Senate, influential senators are asking for a vote on PIPA (the PROTECT-IP Act) to be postponed so the bill can be further reviewed and possibly amended. Additionally, the White House has issued an official response to two petitions calling for President Obama to veto any of this legislation that does pass through Congress, and while he hasn't promised to do so, it does show that the administration is at least thinking about the implications this legislation would have for free expression online.

But the war against SOPA and PIPA is not over yet, in part because a lot of people just don't know all this is happening. To raise awareness, Reddit will be proceeding with a planned "blackout" of the site this Wednesday, in which the normal content will be replaced by an educational message about PIPA/SOPA. Several other sites will be following suit, including Minecraft, ICanHazCheezburger (the whole network of meme sites), BoingBoing and Rasberry Pi. Wikipedia is soliciting contributor input on whether to join as well. If you're a website owner, consider "blacking out" your own site on January 18 to join in the protest.

If you believe, like I do, that these bills are too open-ended and should not be passed, there's still time and reason to contact your senators and representatives. PIPA is scheduled to come up for a vote on January 24, which is just over a week away, and the more calls and letters the senators get, the more likely they are to vote against it. And even though the vote on SOPA has been indefinitely postponed, it still constitutes a looming threat to internet freedom. Don't hesitate to let Congress know who they are supposed to be representing!

2012
Jan
05

Internet access: an enabler of rights

Vint Cerf, one of the inventors of the internet (for real: he helped develop TCP/IP and early email tech) has written an enlightening editorial in the New York Times. His argument is that internet access should not be considered a human right in and of itself; it's an enabler of the right to free speech. Sure it makes sense to protect people's right to internet access, but only insofar as that is a component of the right to free speech.

...technology is an enabler of rights, not a right itself. There is a high bar for something to be considered a human right. Loosely put, it must be among the things we as humans need in order to lead healthy, meaningful lives, like freedom from torture or freedom of conscience. It is a mistake to place any particular technology in this exalted category, since over time we will end up valuing the wrong things.

2011
Nov
28

Mozilla's Call the Senate day

The Mozilla Foundation, the group behind Firefox, is organizing another campaign against the PROTECT-IP Act. This time, they're asking voters to call the Senate next Tuesday (they don't give a date, but I'm guessing this is tomorrow) to register their opposition to the act.

As I've previously written, PROTECT-IP is a bill designed to discourage distribution of copyrighted material online. It would greatly expand the actions that the government is allowed to take with respect to websites or online services that are suspected of being involved in this distribution. There is a widespread concern that the powers granted by this bill are too easily abused, and that they will be ineffective. If you believe, as I do, that this is going too far, please consider contacting your representatives in Congress to let them know.

2011
Nov
22

Internet censorship in the US

Thanks to campaigns like last week's American Censorship day, computer users around the United States (and beyond) have been sitting up and paying attention to two bills regarding online copyright infringement that are now working their way through Congress: SOPA and PROTECT-IP. There is a lot of hype about how the law represented by these bills would be a terrible affront to free speech, and it may or may not be right, but as usual when it comes to legal matters, many people don't have the knowledge to judge for themselves. With this blog post and possibly others like it, I'm trying to get relevant information out there so we can all make more informed decisions.

(Full disclosure: I am personally opposed to the passage of SOPA/PROTECT-IP, but I've tried not to let that bias come through too strongly.)

A brief history of information exchange

Back in the days before internet use was so widespread, media redistribution was not a major problem. If you wanted to share a song or a video with someone, you had to physically lend them a tape, CD, or DVD. Yes, it was possible to make copies of media, but it required specialized equipment, and more importantly, it took time and effort for ordinary people to do. Media distributors, namely the record companies and movie studios, were largely the only ones with the resources to do this efficiently on a large scale.

With the advent of computers, and specifically high-speed internet access, that's no longer true. Now, in order to share some information with someone, you no longer need to hand off an actual physical object. Instead, all your computer needs to do is transfer the state of some transistors (your RAM) into electrical signals in a wire (your modem or network card), basically just shift some electrons around. This is a highly repetitive task, exactly the kind of thing computers can do very efficiently. In other words, copying large amounts of information has suddenly become quick and easy enough that individuals can do it.

To most people, this is a good thing. The entire purpose of the internet is to allow individuals to disseminate information widely: blog posts, tweets, personal photos, status updates, news articles, academic publications, advertisements, and all sorts of other types of content all benefit from having as many people see them as possible. But computers don't distinguish between different kinds of content the way humans do, so technologically speaking, any system that lets people share their blog posts and tweets and so on can be used just as well for sharing music and movies. This represents a problem for the multimedia industry's traditional business model, where they make money from each copy of a CD or DVD that gets sold.

In response, the representative trade organizations for the music and movie industries, the RIAA and MPAA respectively, have used various tactics to try to stop movies and music from being shared between people.

Technological: deep packet inspection

One tactic the media organizations have tried is making computers "smart" enough to pick out copyrighted content from all other internet traffic and stop it in transit. This is called "deep packet inspection" because rather than examining only the header data of each IP packet, which tell where the packet is from and where it's going, computers look "deeper" into the packet, at its actual content. This system requires the coorperation of the tier-1 internet service providers, because they are the ones who control the computers that manage all the data sent over the internet. There was a large public outcry against this system because of the potential for abuse; once the technology to look into packet contents comes into common use for one reason (like catching copyright violations), it becomes almost trivially easy for someone with the right kind of access to use it for another purpose (like silencing political opposition). ISPs have also generally opposed the idea because, although they do use deep packet inspection under limited circumstances, checking every packet that passes through their system requires a lot of computational power. Besides, the use of deep packet inspection to detect copyrighted material in transit was easily nullified by encrypting data before sending it out over the internet, using services like Tor or the SSL encryption that's built into every browser and most web servers.

Legal: the Digital Millennium Copyright Act

When technological measures proved impractical, the media industries shifted their focus from the ISPs to the "online service providers," sites like YouTube or Facebook which actually host user-submitted content that may include music or movie files. To do so, they used the provisions of the Digital Millennium Copyright Act, a 1998 law that governs copyright protection for files and digital data.

Normally, copyright law holds any person or organization which distributes copyrighted material accountable for that distribution. However, there is a piece of the DMCA called the Online Copyright Infringement Liability Limitation Act, commonly known as the "safe harbor provision," which specifies that an online service provider is not legally liable for infringing material uploaded by its users, as long as they remove the content once notified of it.

  1. When a copyright owner finds their copyrighted work posted on a content provider site, they send a DMCA takedown notice to the site's designated DMCA compliance agent
  2. The content provider removes the content and notifies the person who uploaded it
  3. The uploader can dispute the original DMCA takedown notice. Unless a lawsuit is filed within 14 days, the content gets put back up.

The safe harbor provision is what allows sites like YouTube to operate; effectively, they get to pass the legal "blame" for copyright infringement on to their users.

The DMCA does, in principle, allow anyone to get any content taken off a particular website, but only temporarily. A key feature of this procedure is that whenever something gets "flagged" as copyright infringement, the person who uploaded it has to be notified, and has the option to respond and get the content restored. Plus, if a takedown notice turns out to be invalid and it's not just an honest mistake, there are (supposed to be) consequences for the sender of the notice, which discourages sending frivolous DMCA takedown notices.

Economic: MediaDefender

In addition to sending takedown notices to hosting proviers, the RIAA and MPAA also attempted to directly track down users who are publishing copyrighted content and threaten legal action against them. Unlike a large company (YouTube), an individual internet user often doesn't have the resources to fight a court battle to demonstrate that he (or she) isn't doing anything illegal. So most of the time, when random Joe Schmoe gets a notice from the RIAA or MPAA that he's been caught illegally distributing copyrighted material and is getting served with a lawsuit unless he settles for $XXX, he's just going to pay up.

This technique, though kind of sleazy, probably would have been more or less acceptable if it were only used on serious, confirmed copyright infringers. But it went much further than that. The media companies decided to "outsource" the work of tracking down and notifying copyright infringers to a separate company, MediaDefender. MediaDefender, in turn, started using automatic computer programs to detect uploaders of copyrighted content and send out infringement notices. As I alluded to earlier, computer programs aren't smart enough to reliably tell when they've found true copyright infringement and when they haven't. Perhaps you can see where this is going: MediaDefender sent out a lot of threatening letters to people who had done nothing wrong, and in some cases not to people at all. There are stories circulating on the internet about how some researchers got a settlement offer sent to their printer.

The reason this happened is that it's actually very difficult to make the connection between the uploading of a copyrighted file and the real person responsible for it. The way MediaDefender and companies like it typically locate copyright infringers is by connecting to the BitTorrent network and attempting to download a movie. When you use BitTorrent to download something, you have access to the IP addresses of all the other computers you're downloading it from. Each of those is uploading the file, which qualifies as illegal distribution. Or so MediaDefender assumed.

There are a few ways this argument can go wrong, though, which they typically forget to check. For one thing, in some cases the file they were downloading was not even copyrighted material, or if it was, the copyright was not owned by one of MediaDefender's clients. They often checked only based on the name, not by examining the content of the file to see if it was what they thought it was. Secondly, some uploaders connect to the BitTorrent network through a proxy server, or something like Tor. In this case, the IP address the downloader sees is that of the proxy server, which legally is not responsible for the content passing through it.

After the stories went public and people saw how unreliable the techniques for identifying copyright infringers were, the RIAA and MPAA bowed to public pressure and stopped using MediaDefender's services.

SOPA and PROTECT-IP

The latest entry in the war on copyright infringement is the bill known as either SOPA or PROTECT-IP, or more recently the E-PARASITE Act, and yes, those acronyms are exactly as stupid as they sound. All three names refer to more or less the same thing; SOPA or E-PARASITE is the version being considered by the House of Representatives, and PROTECT-IP is the version originally proposed by the Senate. These bills are intented to expand on the DMCA, and generally they provide additional means by which copyright owners (meaning the large media companies) can have content removed from being available online.

But they don't stop there. Rather than just providing for the removal of copyrighted content, as the DMCA did, these bills contain procedures that would basically cripple any website accused of facilitating the distribution of copyrighted material. If SOPA/PROTECT-IP passes, it becomes illegal for any US-based company to advertise on such a website, provide it with a domain name, or allow any payments to be made to it.

Remember, the reason people are concerned about this is not that they want to avoid paying for DVDs. The problem is twofold:

  1. There is a huge potential for these laws to be abused, since they make it possible for anyone (with enough money?) to get material or even entire websites taken offline, without having to prove that they have a legal basis for doing so
  2. There are valid arguments that the whole system of copyright stifles innovation. A lot of progress in art and science is made by building on top of other people's work, and strong copyright enforcement makes that a risky proposition. It's much more difficult to come up with something entirely new.

If nothing else, consider that the list of people and companies who are opposed to SOPA and PROTECT-IP includes everyone from Google to Visa to the technology chief of the European Union to even the Vice President (sort of... indirectly). I'd say they have to have some valid points.

In closing, since one of the core themes of this blog is going to the original source, I'd encourage you to look at the actual text of each bill and put some thought into just how good or bad it would be for economic, artistic, and scientific development. Here are the links again, as of the time of posting:

To see current information on the status of each bill, head to the Library of Congress legislative information site and search for the bill number, either HR 3261 or SR 968.

Further Reading

2011
Jun
13

Turkey update

Last month I posted about an internet censorship/filtering plan proposed by the Turkish government. Well, despite what must be a fair amount of negative publicity, the plan is still in place; Turkey plans to put the internet filter in place on August 22 as originally scheduled.

Now this has attracted the attention of Anonymous, the "global hacker collective" (for lack of a better term). Anonymous is essentially the online equivalent of either freedom fighters or terrorists, depending on who you ask (obviously, I tend to prefer the former description). It's not an organized group, rather it's more like a flash mob: a large number of people who spontaneously cooperate to accomplish some task. Anyway, the point is, if they get mad at you, you're kind of forced to sit up and pay attention.

Anonymous used a DDoS attack (I believe) to overload the servers running the TIB website. Although that doesn't really accomplish much by itself, it does show the Turkish government that they've made some powerful enemies in cyberspace. As much as I hope they'll reconsider after this, I'm not too optimistic.

2011
May
07

Internet censorship and you

There's a movement going around on Facebook to bring attention to a plan by the Turkish government to begin filtering internet access within the country. As of August 22, internet service providers in Turkey will be required to make their users choose one of four access plans, each corresponding to a blacklist of websites that will be blocked. For example, the "domestic" plan will block international websites, and "children" will presumably block anything considered to be inappropriate for kids (pornography and such). But the exact blacklists will be maintained by the BTK (Turkish Information Technologies Board, or something like that), and will not be made public. So the government can theoretically add any website to the blacklists, thereby using them to suppress political opposition or whatever they want, and nobody will know. Any time a government agency gets power without explicit accountability like this, there's a high potential for abuse and people should be concerned. Even if most government workers are really just trying to do what's best for their country, how much do you trust that everyone who ever works in the information technologies agency will be able to resist the temptation to go too far?

Of course, the Turkish government is arguing that this program doesn't restrict anything, it only adds options. The head of the BTK says, "The users who want to access the web freely have the option to select 'standard package'." Without access to the original material released by the Turkish government, I can't tell whether that's really the case, but I have my doubts. At the end of last month, the TÏB (Telecommunications Directorate — see, that even sounds ominous) issued a "request" to internet service providers within the country asking them to ban websites which include any of a set of words, and threatening unspecified punishment if they didn't comply. So it seems that the government is not above using hard-handed censorship methods, even without a clear legal basis to do so. That's the real problem, that the people in power have this better-to-ask-forgiveness-than-permission attitude. The secret blacklist of websites is just going to be a tool that makes that far easier for them to put that attitude into practice. They never have to ask forgiveness if nobody finds out.

So what's a freedom-respecting internet citizen to do about this? A lot of people in Turkey itself are taking to the streets to protest the internet censorship, which will hopefully have some effect. Of course, if the Turkish government is really fixated on this plan, they could just ignore the protests of their citizens. However, it's my understanding that Turkey is interested in joining the European Union, and more generally interested in appearing progressive in the eyes of the "western" world. Ignoring massive protests in the country isn't going to help their case. This also means that citizens of the US and European democracies can perhaps help by contacting their elected officials (at least, to the extent that asking your elected officials to do anything ever has an effect), reminding them to stay aware of the situation in Turkey and to make it clear that ordinary citizens in the US and western Europe don't consider Turkey's behavior appropriate for a modern nation.

Then again, one has to wonder whether the governments of "western" nations are going to chastise Turkey for this, given that a lot of them are already on their way to doing the same thing! Turkey is only the latest in a series of national governments that are instituting programs to restrict internet access. This first made news in 2007, when Australia's Minister of Telecommunications announced that all internet service providers in the country would be required to offer their customers the option of filtered internet access, using a government-controlled, non-public blacklist. The plan sounds uncannily similar to what Turkey is now trying to introduce. This is somewhat worrying because, as Wikipedia reports, the next move by the Australian government was to make some of the filtering mandatory, although after extended public opposition, the government backed down... temporarily. Here's hoping that Turkish protests can produce the same (or a better) result.

Even the United States is on the path toward enforcing internet restrictions using a non-public blacklist. Last year, the office of Immigration and Customs Enforcement, a division of the Department of Homeland Security, asserted that it had the right to disable any domain that, by its own judgment, was involved in illegal activity, focusing on copyright infringement, counterfeiting, and child pornography. From a technical standpoint, this isn't quite as restrictive as the filtering schemes being considered in Australia and Turkey, since the ICE isn't blocking the websites themselves, just preventing them from being accessed using their domain names. It's possible to get around that, if you know the site's numeric IP address, and in fact there is a Firefox plugin, MAFIAA Fire, to do just that. But the motivation is the same, and I bet the DHS would try all-out web filtering if they thought they could get away with it. And if they don't see enough resistance to what they're doing now, that's exactly what they will think.

Thankfully, Mozilla (the creators of Firefox) are standing up to the DHS. When the Homeland Security people asked Mozilla to disable the MAFIAA Fire plugin, Mozilla responded by asking for the legal basis of the request. So far, there has been no response — you have to wonder whether they can actually justify this request at all. This is the kind of behavior that we need to see more of: all too often, when the government makes a request to an ISP or content host to have something taken down, they just do it without asking any questions, and the government gets free rein to have anything it wants censored. Don't let them get away with it! While I'm not saying we should cripple our government's ability to enforce the law, we do have the right — and even the responsibility — to remind them that they also have to obey the law.

For anyone who's concerned about this, let me offer a few closing notes:

  • Developments in these internet censorship programs are usually reported by Slashdot whenever they become public. You can subscribe to the RSS feed (this feed focuses specifically on internet users' rights), or follow the stories on Facebook or Twitter.
  • So far, the internet filters being proposed center on websites (things you access in a web browser). That suggests that other services that run over the internet, like chat/instant messaging, BitTorrent, and Skype, are free to continue, at least for now. In the event that web filtering gets put in place, those alternate services can still be used to communicate. Of course, Turkey (or any other nation) could attempt to block these other services, but many of them are designed in such a way as to make that technically difficult. Besides, shutting off something like Skype cannot be justified as protecting people from obscene or illegal content — that's straight-up censorship, and once the news of that got out, there would be no illusions in the international community that Turkey is doing this to assert control, not just to protect its people.
  • The Tor Project provides software that implements an "onion router": it masks the true nature of internet communications by routing data packets around a maze of connected servers and encapsulating them in multiple layers of encryption. Any kind of internet traffic (whether web browsing, file transfer, chat, etc.), once it gets sent into the Tor network, is indistinguishable from any other kind, so the only way for a government to stop it is to cut a country off from internet access entirely. If you operate a web server or any computer with constant internet access and have some bandwidth to spare, you can help the project out by running a relay node on your server. Check out the series I posted a couple years ago, when the Tor project helped circumvent Iran's internet access restrictions, about my experience setting up a relay.

And finally, for people who aren't concerned about this: I won't argue that you should be. Everybody gets to pick their own pet issues. But remember, the goal here is to keep a government honest, and to do that requires as much public pressure as possible. If you don't actively agree that governments should be able to maintain and enforce private website blacklists, any little thing you do to remind people that this is going on — a Facebook status update, a tweet, a mention to a friend — can be a big help.