<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xml:base="http://haverkamp.com" xmlns:dc="http://purl.org/dc/elements/1.1/">
<channel>
 <title>Otherwise Occupied - cyberspace_law</title>
 <link>http://haverkamp.com/taxonomy/term/165/9</link>
 <description></description>
 <language>en</language>
<item>
 <title>Internet anonymity ain&#039;t dead yet.</title>
 <link>http://haverkamp.com/2007/03/21/internet-anonymity-aint-dead-yet</link>
 <description>&lt;p&gt;[The following was largely spawned by a Cyberspace Law class last night, and the repeated suggestions that we must authenticate users before we allow them to &quot;use the Internet&quot; so that we may track down evildoers.]&lt;/p&gt;
&lt;p&gt;Are we really heading toward the end of a (relatively) anonymous Internet?  I don&#039;t think so.&lt;/p&gt;
&lt;p&gt;To properly answer this, it&#039;s important to consider how the Internet is constructed.  Sure, you&#039;ll often read accounts of your data traveling across the Internet&#039;s &quot;backbone.&quot;  The problem is, there isn&#039;t a single backbone.  The internetwork that is the Internet is comprised of numerous independent network backbones that interconnect.  For any one node on any one of those backbones to identify with any certainty the sender of a packet would require a vast identity infrastructure that simply is nowhere near existence.  However, it&#039;s possible that this extreme example of the impossibility of defeating anonymity is more than what some consider necessary.  In fact, I know it is, based on class discussion.&lt;/p&gt;
&lt;p&gt;Let&#039;s take another popular example that has been used: all users must authenticate their identities before they are allowed to &quot;connect to the Internet.&quot;  The obvious first question I have to ask is &quot;To whom must they authenticate?&quot;  This is not an easy question to answer.&lt;/p&gt;
&lt;p&gt;Is the answer the user&#039;s Internet Service Provider?  If so, who&#039;s going to mandate that?  If it&#039;s the ISP who mandates this, what other limitations of service will the ISP then have to place on the user to enforce this authentication?  A user who wishes to remain anonymous will simply tunnel traffic through an anonymizing conduit, whether this is an application like TOR, or wilder approaches like tunneling one application layer protocol through another.&lt;/p&gt;
&lt;p&gt;This raises another problem: who authenticates the conduit?  Not all Internet &quot;users&quot; are discrete individuals.  Many are servers providing services, remote access devices providing connectivity, or bots gathering and processing data.  Who authenticates every process that connects to the Internet?  Who do these processes authenticate to?&lt;/p&gt;
&lt;p&gt;Finally, are users going to be expected to authenticate to every peer process?  This suggests that every process and every user on the Internet will use a single authentication mechanism, or sufficient federation will have to exist for these authentications to take place.  Who&#039;s going to write the software that allows the millions of autonomous servers, routers, switches, and other devices connected to the Internet to be able to carry out these authentications so that anonymous actors may eventually be identified?&lt;/p&gt;
&lt;p&gt;My point is this: until everything authenticates, there is no forced, universal authentication to &quot;connect&quot; to the Internet.  As long as unauthenticated systems exist, and as long as owners of some of those systems prize anonymity, a step as limited as forcing users to properly authenticate to an ISP before using the Internet (a concept that has still more questions) will not kill one&#039;s ability to act anonymously, nor will it lead to discoverable identification of anonymous sources.&lt;/p&gt;
</description>
 <comments>http://haverkamp.com/2007/03/21/internet-anonymity-aint-dead-yet#comment</comments>
 <category domain="http://haverkamp.com/topics/anonymity">anonymity</category>
 <category domain="http://haverkamp.com/topics/cyberspace-law">cyberspace_law</category>
 <category domain="http://haverkamp.com/taxonomy/term/57">Internet</category>
 <category domain="http://haverkamp.com/topics/privacy">privacy</category>
 <pubDate>Wed, 21 Mar 2007 13:09:51 -0600</pubDate>
 <dc:creator>gregh</dc:creator>
 <guid isPermaLink="false">458 at http://haverkamp.com</guid>
</item>
<item>
 <title>The neighborhood was never beautiful enough</title>
 <link>http://haverkamp.com/2007/02/07/the-neighborhood-was-never-beautiful-enough</link>
 <description>&lt;p&gt;In Cyberspace Law tonight, we discussed &lt;i&gt;Sony v. Universal City Studios&lt;/i&gt;, the Betamax case.  The Court mentions the testimony of Fred &quot;Mr.&quot; Rogers at the trial court, and Prof. Freiwald brought it up, first ensuring that we knew who he was.  I knew.  Oh, yes.  I knew.&lt;/p&gt;
&lt;p&gt;&quot;Mr. Rogers&quot; was filmed at WQED in Pittsburgh.  WQED was on Fifth Ave., between the dorm and apartment complex I lived in.  Meanwhile, Fred Rogers lived in a condo on the opposite side of Carnegie Mellon&#039;s campus.&lt;/p&gt;
&lt;p&gt;I heard lots of stories about how he often walked across the campus from his condo to WQED, often graciously stopping to talk to students who spoke to him.  I was on the lookout myself.  I was a big fan growing up, and I especially always wanted a train running from room-to-room, though my mean, uncaring parents never acquiesced.&lt;/p&gt;
&lt;p&gt;Alas, not once did I catch him cutting across the Cut.  Or strolling down Morewood Avenue past Mudge Hall.&lt;/p&gt;
</description>
 <comments>http://haverkamp.com/2007/02/07/the-neighborhood-was-never-beautiful-enough#comment</comments>
 <category domain="http://haverkamp.com/topics/cmu">cmu</category>
 <category domain="http://haverkamp.com/topics/cyberspace-law">cyberspace_law</category>
 <category domain="http://haverkamp.com/topics/law-school">Law_School</category>
 <pubDate>Wed, 07 Feb 2007 01:23:42 -0600</pubDate>
 <dc:creator>gregh</dc:creator>
 <guid isPermaLink="false">438 at http://haverkamp.com</guid>
</item>
</channel>
</rss>
