[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: SSL CHALLENGE: 0.11 borken?

To: [email protected]
Subject: Re: SSL CHALLENGE: 0.11 borken?
From: Piete Brooks <[email protected]>
Date: Thu, 24 Aug 1995 21:40:35 +0100
Cc: [email protected], [email protected], [email protected]
In-Reply-To: Your message of Thu, 24 Aug 1995 16:05:16 -0400. <[email protected]>
Sender: [email protected]

>    I had several machines running brloop 0.03 and brclient 0.11, and
> none of them appeared to be sending ACKs back to the server.

The probability of getting an ACK back is indeed small :-((

> Is this a known problem?

yes -- this is why all the WWW pages and my messages to cypherpunks say
"please get the latest code" ...

> It might account for the large number of unACKed keyspaces.

I fear so :-((

> brloop 0.04 and brclient 0.12 seem to work well, however.

Whew !

brclient 0.13 is now out to try to track down the problem which is causing the
comgestion ...

It seems that old brloop's keep calling the server, and sending HELO, COMM and
then QUIT (Greet, Introduce, Part) i.e. not actually do anything :-(
[ Some only manage "HELO" or "HELO COMM" ]

These systems are hammering the server, and I suspect are the cause of the
congestion. I have added more logging to brclient 0.13, and it has caused the
problem to disappear ...

Follow-Ups:
- Re: SSL CHALLENGE: 0.11 borken?
  - From: Thomas Grant Edwards <[email protected]>

References:
- Re: SSL CHALLENGE: 0.11 borken?
  - From: [email protected]

Prev by Date: BruteSSL: WTF? 0c2b-cf7a NOACK 0c2b 50000 Joe Thomas <[email protected]>
Next by Date: Re: SSL CHALLENGE: ALERT! probable misallocation of keys?
Prev by thread: Re: SSL CHALLENGE: 0.11 borken?
Next by thread: Re: SSL CHALLENGE: 0.11 borken?
Index(es):
- Date
- Thread