{"id":706,"date":"2011-07-21T15:43:39","date_gmt":"2011-07-21T20:43:39","guid":{"rendered":"http:\/\/blogs.law.harvard.edu\/herdict\/?p=706"},"modified":"2011-07-22T07:23:45","modified_gmt":"2011-07-22T12:23:45","slug":"telex-deep-packet-inspection-for-good","status":"publish","type":"post","link":"https:\/\/archive.blogs.harvard.edu\/herdict\/2011\/07\/21\/telex-deep-packet-inspection-for-good\/","title":{"rendered":"Telex: Deep Packet Inspection for Good"},"content":{"rendered":"
This week, the Internet was abuzz with news of a new censorship circumvention measure. That would be Telex<\/a>– the system proposed by researchers at the University of Michigan to get around traditional censorship measures. It\u2019s currently only a proof of concept, however, we\u2019re excited about its future.Telex’s promise is its difference from other anti-censorship and circumvention technologies. Most current anti-censorship technologies focus on proxy servers or tunneling, which relies upon the creation of an encrypted connection between users’ computers and non-censored networks and servers, thereby re-routing traffic to non-censored sites. Programs such Tor conceal users’ online identities and allow individuals to access sites anonymously through secure connections; however, low-latency anonymity networks have yet to develop the technology to protect users from being monitored as they enter and exit these networks.
\nTunneling is likewise limited in its scope, as censors are constantly compiling lists of new proxy servers to block. Moreover, it is difficult to broadcast information about proxy servers without alarming\/alerting the censors; individuals seeking to evade censorship are likely to come by information of these “tunnels” by means easily accessible to any tech-savvy censor.<\/p>\n

Telex’s major development is the absence of any easily identifiable, and therefore blockable, entry site. Users download the Telex application and, when they want to visit a blocked website, utilize the application to establish an HTTPS connection to non-censored sites<\/p>\n

First, the user routes their traffic to a site that has a Telex enabled router between it and the user. If Telex is embraced by ISPs within anti-censorship countries, like Germany, the Netherlands or the United States, this means any SSL connection that goes through these websites will become an instant anti-censorship beacon. SSL is commonly used for online banking, commercial transactions, as well as email and other communication mechanisms. To our knowledge at Herdict, no country has permanently blocked all HTTPS sites.<\/p>\n

Using the Telex software, the user generates a cryptographic tag to put in the headers of packets to normal SSL sites. Using deep packet inspection, the Telex router finds each tagged packet. Deep packet inspection, which is a method that allows an ISP to see the destination and content of a user\u2019s traffic, is often used for evil, i.e. censorship or filtering. However, in the proposed Telex structure, it\u2019s used for good.<\/p>\n

As Timothy B. Lee from Ars Te<\/a>chnica <\/a>writes,<\/p>\n

\n

\u201cThe system accomplishes this using a clever tweak to the TLS handshake that occurs whenever a browser initiates an encrypted Web connection. One of the steps in that handshake requires the client to choose a random bit string known as a “nonce.” If a client wants Telex to redirect the connection, it uses Telex’s public key to generate a steganographic “tag.” The tag format is carefully chosen so that someone who knows the Telex private key will be able to recognize the tag efficiently\u2014but no one else will be able to distinguish it from a random string.\u201d<\/p>\n<\/blockquote>\n

The Telex software on the ISP-side (in another country) routes these tagged packets to TOR or a proxy\/tunneling\u00a0site. The end-to-middle proxy scheme cuts down on the lag time and the possibility of a censorship regime blocking proxies.<\/p>\n

Telex currently is in its proof of concept phase, so there are t<\/a>echnical issues <\/a>that will have to be resolved. \u00a0Currently, more testing is needed for Telex connections to mimic the behavior of normal SSL browsing, so that countries can\u2019t detect Telex users. Similarly, Telex only currently supports a single SSL site to access blocked site through, which could also tip off countries that are used to monitoring Internet access.<\/p>\n

There are also wider implementation issues. In order for it to be effective, Telex-enabled routers would have to exist upstream of most to all connections in a country. \u00a0Also, wide spread implementation would probably depend on Western governments mandating usage by ISPs, due to costs and political implications. \u00a0We look forward to seeing whether Telex can move from proof of concept to reality.<\/p>\n<\/div>\n","protected":false},"excerpt":{"rendered":"

This week, the Internet was abuzz with news of a new censorship circumvention measure. That would be Telex– the system proposed by researchers at the University of Michigan to get around traditional censorship measures. It\u2019s currently only a proof of concept, however, we\u2019re excited about its future.Telex’s promise is its difference from other anti-censorship and […]<\/p>\n","protected":false},"author":3785,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"jetpack_post_was_ever_published":false,"_jetpack_newsletter_access":"","_jetpack_dont_email_post_to_subs":false,"_jetpack_newsletter_tier_id":0,"_jetpack_memberships_contains_paywalled_content":false,"_jetpack_memberships_contains_paid_content":false,"footnotes":"","jetpack_publicize_message":"","jetpack_publicize_feature_enabled":true,"jetpack_social_post_already_shared":false,"jetpack_social_options":{"image_generator_settings":{"template":"highway","default_image_id":0,"font":"","enabled":false},"version":2}},"categories":[1],"tags":[],"class_list":["post-706","post","type-post","status-publish","format-standard","hentry","category-uncategorized"],"jetpack_publicize_connections":[],"jetpack_featured_media_url":"","jetpack_sharing_enabled":true,"jetpack_shortlink":"https:\/\/wp.me\/p4LdGs-bo","_links":{"self":[{"href":"https:\/\/archive.blogs.harvard.edu\/herdict\/wp-json\/wp\/v2\/posts\/706","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/archive.blogs.harvard.edu\/herdict\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/archive.blogs.harvard.edu\/herdict\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/archive.blogs.harvard.edu\/herdict\/wp-json\/wp\/v2\/users\/3785"}],"replies":[{"embeddable":true,"href":"https:\/\/archive.blogs.harvard.edu\/herdict\/wp-json\/wp\/v2\/comments?post=706"}],"version-history":[{"count":2,"href":"https:\/\/archive.blogs.harvard.edu\/herdict\/wp-json\/wp\/v2\/posts\/706\/revisions"}],"predecessor-version":[{"id":709,"href":"https:\/\/archive.blogs.harvard.edu\/herdict\/wp-json\/wp\/v2\/posts\/706\/revisions\/709"}],"wp:attachment":[{"href":"https:\/\/archive.blogs.harvard.edu\/herdict\/wp-json\/wp\/v2\/media?parent=706"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/archive.blogs.harvard.edu\/herdict\/wp-json\/wp\/v2\/categories?post=706"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/archive.blogs.harvard.edu\/herdict\/wp-json\/wp\/v2\/tags?post=706"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}