On Tuesday 22 January 2008 19:41, [EMAIL PROTECTED] wrote: > On Jan 22, 2008 8:25 PM, Matthew Toseland <[EMAIL PROTECTED]> wrote: > > On Tuesday 22 January 2008 18:40, [EMAIL PROTECTED] wrote: > > > If Frost receives ALL_DATA_NOT_FOUND, it keeps retrying this index > > > during next board updates. > > > But the current DoS attack uses many ADNF, and together with the > > > backload (days to download backward) > > > it takes ages until a board completes to update. > > > > I thought he was pointing them to a GIF / some evil content he inserted block > > by block... > > He lately switched to 'redirects to nowhere'. This is what I get from > the node. >90% ADNF.
That's interesting, it means he hasn't yet figured out how to redirect each post to a single key within a target splitfile - or he doesn't want to fill up our datastores with any specific content. > > > > > > My question is: what is a good way to re-request keys that got an > > > ADNF? Try it exactly X times, > > > or keep it trying if we request keys for today, but don't try them > > > again if we download messages for > > > previous days, or what? I know, in theory those keys could finally > > > arrive after weeks, so what logic should > > > we use? > > > > Try it at some point in the vague future I suppose was the original idea. You > > could set max retries to 3 and never retry on ADNF, if the messages are > > reasonably expendable. > > "if the messages are reasonably expendable." ??? Plainly retrying slightly increases the chances of fetching a valid message. It's a tradeoff. > > > > bback.
pgpU1h2Dp2ZBR.pgp
Description: PGP signature
_______________________________________________ Devl mailing list [email protected] http://emu.freenetproject.org/cgi-bin/mailman/listinfo/devl
