<span>Co</span>uldn't you just make your node a middleman and ban tor from connecting to your Internet One Connection?<br>Comrade Ringo Kamens<br><br><div class="gmail_quote">On Jan 9, 2008 12:40 PM, Nathaniel Fairfield <
<a href="mailto:than@cmu.edu">than@cmu.edu</a>> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div class="Ih2E3d">F. Fox wrote:
<br>> Another thing: How would the PKI work over Internet2? AFAIK, Tor needs<br>> to be able to talk to an authoritative directory server; also, the<br>> directory it gets would be full of Internet1 (as I'll refer to the
<br>> "normal" Internet here) nodes.<br>><br>> Clearly, an entirely new PKI would have to be set up, via forcing<br>> options in copies of Tor (including, among other things, forcing a few<br>> copies into authoritative directory mode). It would be an interesting
<br>> project, but it would take quite a bit of work.<br><br></div>I wasn't thinking of setting up an entirely separate Tor network on<br>Internet2. As I mentioned, I2 is transparent for my machine: when I<br>connect to another machine (google, whatever), it will use I2 if
<br>possible and fall back to standard internet otherwise.<br><br>So I was hoping to exploit the fact that several of the main Tor nodes<br>(at MIT, Harvard, etc) are on I2, and I could relay a *lot* of traffic<br>between such nodes. The problem is that I need to explicitly restrict
<br>my relay to those nodes because my standard internet access is bandwidth<br>limited.<br><font color="#888888"><br>Nathaniel<br></font></blockquote></div><br>