The problem is that this changes the expected time to reply, which means
that it is a protocol change since it will result in nodes being angry at
each other for no reason should one have implemented it and not the other.
I do agree that we need to move this up to the top of the list though (I
must say I find it a little amusing that requesting the data was the
"fundamental flaw in Freenet" that the maker of "mediaenforcer" guy
claimed to have found.)
(I'm going to send my $200 worth (inflated holiday pricing) on the whole
"cluster" debacle as soon as I have gone for a walk in the fresh snow.)
On Sun, Dec 24, 2000 at 09:55:01AM -0800, Ian Clarke wrote:
> Ok, so this media enforcer thing has churned up one issue that we
> should address to lay the thing to rest, namely the danger of
> identifying whether a node is caching content using a HTL of 1. The
> way to counter this is to introduce some randomness into whether a HTL
> is decremented or not. If this hasn't been done already, we should
> perhaps make the change before this release 0.3.6 (which I will do
> tonight PST).
>
> Ian.
--
'DeCSS would be fine. Where is it?'
'Here,' Montag touched his head.
'Ah,' Granger smiled and nodded.
Oskar Sandberg
[EMAIL PROTECTED]
_______________________________________________
Freenet-dev mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/mailman/listinfo/freenet-dev
