<div>ok...thanks for the clarification. I thought that "tunnel" meant less hops but that was a misunderstanding on my part. So it all comes down to the bit encryption per packet.</div>
<div> </div>
<div>Thanks!</div>
<div>Chris<br><br></div>
<div class="gmail_quote">On Fri, May 16, 2008 at 4:28 PM, yousifnet <<a href="mailto:yousifnet@gmail.com">yousifnet@gmail.com</a>> wrote:<br>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">
<div class="Ih2E3d">> First, my understanding of SSL is that it creates a direct tunnel from<br>> your computer to the web server (or router if the SSL certificate is bound to<br>> somthing like a load-balancing router). If this is correct, wouldn't this "short<br>
> circuit" the TOR purpose of obfuscation?<br><br></div>[Normal SSL]<br>A) user sends encrypted message to proxy<br>B) proxy forwards the message to the server<br>C) server responds with another encrypted message to the proxy<br>
D) proxy forwards the encrypted message to the user<br>E) proxy can't read or change anything in between<br><br>USER <<===>> PROXY <<===>> SERVER<br><br>[Tor with SSL]<br>A) Same as above. The proxy can be more than one server(two, three servers,etc.)<br>
B) proxies still can't read anything (semi-redundant but that's another story)<br><br>USER <<==>> PROXY1<<==>> PROXY2 <<==>> PROXY3 <<==>> SERVER<br></blockquote></div>
<br><br clear="all"><br>-- <br>Interested in selling your home? Ask me!