<div>No, the middle node cannot change data. It can, however, randomly cut out and drop circuits, connections, or drop off the face of the earth entirely. That is probably what was happening to him. The middle node essentially knows nothing (other than who the entry and exit nodes are), so there would be no benefit to doing so either.</div>
<br clear="all"> - John Brooks<br>
<br><div class="gmail_quote">On Wed, Feb 18, 2009 at 6:09 PM, Mitar <span dir="ltr"><<a href="mailto:mmitar@gmail.com">mmitar@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
Hi!<br>
<div class="Ih2E3d"><br>
On Tue, Feb 17, 2009 at 11:32 PM, Scott Bennett <<a href="mailto:bennett@cs.niu.edu">bennett@cs.niu.edu</a>> wrote:<br>
> In the particular case I was describing, the node that was consistently<br>
> appearing in the circuits that cut off files happened not to be an exit in<br>
> any of the failure cases. IIRC, it was nearly always in a middleman position,<br>
> though I think there was a day when it was an entry guard.<br>
<br>
</div>Middle node can change payload without next node noticing that? There<br>
is not checksuming/signing in the process?<br>
<font color="#888888"><br>
<br>
Mitar<br>
</font></blockquote></div><br>