I added a board update information to the current Frost code in svn (very alpha).
It shows some stats about the about progress per board and day. I run it for just 1 or 2 hours now, see the stats for today and yesterday: most of them are ADNF. Board: frost Date : 2008.1.22 Informations for current session: countTriedIndices : 104 currentIndex : 328 maxIndex : 328 maxSuccessfulIndex: -1 countADNF : 99 countDNF : 0 countInvalid: 5 countValid : 0 ------------------------------------------------------- Board: frost Date : 2008.1.21 Informations for current session: countTriedIndices : 106 currentIndex : 349 maxIndex : 349 maxSuccessfulIndex: -1 countADNF : 102 countDNF : 1 countInvalid: 3 countValid : 0 ADNF is the problem. On Jan 22, 2008 7:40 PM, <bbackde at googlemail.com> 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. > > 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? > > bback. > -- __________________________________________________ GnuPG key: (0x48DBFA8A) Keyserver: pgpkeys.pca.dfn.de Fingerprint: 477D F057 1BD4 1AE7 8A54 8679 6690 E2EC 48DB FA8A __________________________________________________
