Which results in: a) Weakening the benefits of the "Unrequest" since, presumably, the node will reply with the bad data during this period, allowing it to spread (and remember, if you are using KHKs then you are fucked ones you got the bad data, you can't request again and hope for better luck). I think that with a little luck a cancer node could do massive damage within a few hours.
b) Making Unrequest much moe difficult to implement, since the longer time since the request, the more difficult it will be to reset things (what was the old reference? where should it be in the stack?). I still think the solution is to allow "Unrequest" only on reference entries. On Fri, 19 May 2000, Ian Clarke wrote: > > > I still think that the same problem is solved by filtering hits based on > > > signatures and I prefer filtering to unrequesting. > > In light of the Request, Unrequest, Request (RUR) attack, I'm going to > > have to agree. > > Don't give up so easily - this attack is countered by delaying > implementation of the unrequest for a few hours after it has been > received. > > Ian. > > _______________________________________________ > Freenet-dev mailing list > Freenet-dev at lists.sourceforge.net > http://lists.sourceforge.net/mailman/listinfo/freenet-dev -- Oskar Sandberg md98-osa at nada.kth.se _______________________________________________ Freenet-dev mailing list Freenet-dev at lists.sourceforge.net http://lists.sourceforge.net/mailman/listinfo/freenet-dev
