// COMPLETE THREAD

Re: SSL CHALLENGE: 0.11 borken?

3 expanded posts · every known parent and child

NODE e9481d48Re: SSL CHALLENGE: 0.11 borken? jered@MIT.EDUThu, 24 Aug 95 13:05:36 PDT

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.  Is this
a known problem? It might account for the large number of unACKed
keyspaces.

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

--Jered
jered@mit.edu

NODE 1d9f8e51Re: SSL CHALLENGE: 0.11 borken? Piete Brooks <Piete.Brooks@cl.cam.ac.uk>Thu, 24 Aug 95 13:41:18 PDT

>    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 ...

NODE 9a1b82c6Re: SSL CHALLENGE: 0.11 borken? Thomas Grant Edwards <tedwards@src.umd.edu>Thu, 24 Aug 95 14:11:45 PDT

Just downloaded the newest stuff and got:

usage: brutessl [-q] <filename> <checksum> <start segment> <no of segments>
       brutessl [-q] -r <filename> [<no of segments>]
       brutessl [-q] -t [<hours>[:<minutes>]]

usage: brutessl [-q] <filename> <checksum> <start segment> <no of segments>
       brutessl [-q] -r <filename> [<no of segments>]
       brutessl [-q] -t [<hours>[:<minutes>]]

usage: brutessl [-q] <filename> <checksum> <start segment> <no of segments>
       brutessl [-q] -r <filename> [<no of segments>]
       brutessl [-q] -t [<hours>[:<minutes>]]

usage: brutessl [-q] <filename> <checksum> <start segment> <no of segments>
       brutessl [-q] -r <filename> [<no of segments>]
       brutessl [-q] -t [<hours>[:<minutes>]]

usage: brutessl [-q] <filename> <checksum> <start segment> <no of segments>
       brutessl [-q] -r <filename> [<no of segments>]
       brutessl [-q] -t [<hours>[:<minutes>]]

Server not responding: Timed out

What do you make of that? (I'm running Linux)

-Thomas