[RC5] First impressions

gindrup at okway.okstate.edu gindrup at okway.okstate.edu
Tue Mar 3 13:56:01 EST 1998

     There are multiple issues.
     Returning duped blocks is irrelevant since the duped-block "attack" 
     late in RC5-56.  Duped blocks are now ignored.
     All keys in all blocks will be eventually cracked by the brute force 
     method employed by D.Net.  If the key is out there, it will be 
     If there are time limits involving money, it is also preferable to 
     reduce the turnaround time for blocks so that the probability that a 
     cracked winning key is sitting in an out-buff when one of the limits 
     expires is minimized.
     The long recent discussion was about the (putative) effect that very 
     large in-buffs have for increasing the block turnaround time.  Both 
     camps were effectively told to drop it by our recently departed List 
            -- Eric Gindrup ! gindrup at Okway.okstate.edu

______________________________ Reply Separator _________________________________
Subject: Re: [RC5] First impressions 
Author:  <rc5 at llamas.net > at SMTP
Date:    3/3/98 8:43 AM

On Mon, 2 Mar 1998, Paul Ross wrote:
> Then, of course, that brings up another question, maybe one more suited to 
> debate than a general moan over the quality of the website ;) Does d.net want 
> to recruit people who are likely to delete the software halfway through a 
> keyblock and never return the results, leaving that block to wait until the 
> re-issue at the end?
Summary from a recent (and far too lengthy) debate: Any block is as likely 
to contain the winning key as any other block. It doesn't matter what 
people do with buffers, as long as they aren't returning duped blocks.
        -Matt Chatterley
     Spod: http://user.super.net.uk/~neddy/spod/spod.html 
To unsubscribe, send 'unsubscribe rc5' to majordomo at lists.distributed.net
rc5-digest subscribers replace rc5 with rc5-digest

More information about the rc5 mailing list