On Tue, Nov 05, 2002 at 08:03:27PM -0500, Zlatin Balevsky wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
>
> | high if it's a big freesite. The correct response is to implement
> | mixmastered first two hops, which we will not implement before 1.0.
>
> This is all nice and good, but
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
| high if it's a big freesite. The correct response is to implement
| mixmastered first two hops, which we will not implement before 1.0.
This is all nice and good, but please consider raising the defaults
even if by just a little _now_. It will hel
Matthew Toseland wrote:
>Fixed default HTL is evil. Add (signed) a random number to each request.
Even that is not sufficient. If you access a site with lots of images
and many of the requests go through a particular node, then it can
deduce a probability for you being the originator, which get
On Tue, Nov 05, 2002 at 10:31:06AM +0100, Tld wrote:
>
> Zlatin Balevsky wrote:
>
> >The network is getting bigger and bigger. Most of my requests DNF with
> >htl 15 but are retrieved with 25. Maybe its time to up the defaults a bit.
>
> There is a bigger problems with actual implementation of
Zlatin Balevsky wrote:
The network is getting bigger and bigger. Most of my requests DNF with
htl 15 but are retrieved with 25. Maybe its time to up the defaults a bit.
There is a bigger problems with actual implementation of HTLs: unless a
node operator explicitly asks otherwise, all reque
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
The network is getting bigger and bigger. Most of my requests DNF with
htl 15 but are retrieved with 25. Maybe its time to up the defaults a bit.
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.0.7 (GNU/Linux)
Comment: Using GnuPG with Mozilla - htt
