While this seems good for lots of circumstances, you have to realise that this does stop people from using sites that use IP address authentication or require you to re-login every time you change your IP. Perhaps this could be an option provided in a checkbox?
<br><br>
<div><span class="gmail_quote">On 5/15/06, <b class="gmail_sendername">glymr</b> <<a href="mailto:glymr_darkmoon@ml1.net">glymr_darkmoon@ml1.net</a>> wrote:</span>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">-----BEGIN PGP SIGNED MESSAGE-----<br>Hash: RIPEMD160<br><br>I forgot one extra idea - that of generating a number of different
<br>circuits to be used at any one time (generation could be spaced say 5<br>minute intervals by the client, circuits more than 4 or maybe 5<br>generations back could be expunged in a fifo type arrangement) that,<br>whenever possible will select a random route to establish any new
<br>connection from one of the number of circuits that are built. The<br>purpose of this specifically is to address the reduction of timing<br>attacks that are possible against a website - if the client sets up say<br>3-6 different circuits to retrieve the various different components of a
<br>web page, each circuit will have a different time signature (due to the<br>viscisitudes of the network) and will make it harder to definitively<br>establish the origin. (and of course every node being both client and<br>
server further obscures this)<br>-----BEGIN PGP SIGNATURE-----<br>Version: GnuPG v1.4.3 (MingW32)<br><br>iD8DBQFEaKa9GkOzwaes7JsRAw1WAJ4w6ksGA9bub++V4DUbPWGR84ATTwCffqPg<br>lhdTd8Jzh9YZTa8Ukhbkq/8=<br>=sPG/<br>-----END PGP SIGNATURE-----
<br></blockquote></div><br>