Re: Cypherpunk Brute Squad [Re: SSL Challenge: Server problems]

> current requirements
> ====================
> 
> PLEASE ensure that you are using a brclient of at least 0.14
> ("grep comment.inffo brclient" to discover what you are using)
> You can updare brclient while brloop is running.
> Some people are still running old versions, and this is hammering the server.
> 
> It also helps to run at least brloop 0.05 ("grep BRLOOPCOMMENT brloop").
> 

Unfortunately the web page under "Socket based key doler" points 
at brclient 0.13 and brloop 0.04.  Could you fix this please:)

Thanks,

Patrick
   _______________________________________________________________________
  /  These opinions are mine, and not Verity's (except by coincidence;).  \
 |                                                       (\                |
 |  Patrick J. Horgan         Verity Inc.                 \\    Have       |
 |  patrick@verity.com        1550 Plymouth Street         \\  _ Sword     | 
 |  Phone : (415)960-7600     Mountain View                 \\/    Will    | 
 |  FAX   : (415)960-7750     California 94303             _/\\     Travel | 
  \___________________________________________________________\)__________/

>> PLEASE ensure that you are using a brclient of at least 0.14
>> ("grep comment.inffo brclient" to discover what you are using)
>> You can updare brclient while brloop is running.
>> Some people are still running old versions, and this is hammering the 
server.
>> 
>> It also helps to run at least brloop 0.05 ("grep BRLOOPCOMMENT brloop").
> Unfortunately the web page under "Socket based key doler" points 
> at brclient 0.13 and brloop 0.04.  Could you fix this please:)

I had a similar report before, and it turned out to be an over zealous WWW 
"cache" :-((

HOWEVER: there is now a new brclient 0.17 which should go faster that pre 0.16 
over "slow" links, but shoudl also work over "fast" links (which 0.16 
sometimes did not).  SO: all 0.16 users should upgrade, just in case the link 
goes fast!

| > those who have logs
| > ===================

    [about manually updating ACKs]

Unfortunately, I don't dare do that, since my machines has crashed
a few times. (nightly reboots for example.)

I guess you dare do it if there is a no-line in the log.

Couldn't you insert some code that measures the time it has taken
that particular IP-number to ACK other block, and timeout the
reservation after double that time or something similar? In this case
you don't run the risk of ACKing a block with the key in it.

Some more work for the server! :-)

/Christian