1995-08-24 - Re: Linux brutessl client

Header Data

From: Piete Brooks <Piete.Brooks@cl.cam.ac.uk>
To: zinc <zinc@zifi.genetics.utah.edu>
Message Hash: 9e8664d755db9ee4317205f66c301e0d83e294451cbe22e93b483b49ab4b019d
Message ID: <“swan.cl.cam.:164680:950824065040”@cl.cam.ac.uk>
Reply To: <Pine.LNX.3.91.950823233650.3783J-100000@zifi.genetics.utah.edu>
UTC Datetime: 1995-08-24 06:51:01 UTC
Raw Date: Wed, 23 Aug 95 23:51:01 PDT

Raw message

From: Piete Brooks <Piete.Brooks@cl.cam.ac.uk>
Date: Wed, 23 Aug 95 23:51:01 PDT
To: zinc <zinc@zifi.genetics.utah.edu>
Subject: Re: Linux brutessl client
In-Reply-To: <Pine.LNX.3.91.950823233650.3783J-100000@zifi.genetics.utah.edu>
Message-ID: <"swan.cl.cam.:164680:950824065040"@cl.cam.ac.uk>
MIME-Version: 1.0
Content-Type: text/plain


> the perl code doesn't seem to work quite right for me though, giving 
> errors when i try to use more than one option at a time, ie.
> Identifier "main::dkltrc4" used only once: possible typo.

Sorry about that ....

I discovered that there was a problem with "require" under perl 5.001
(if one does a require on getopts.pl, the perl CRASHES with some flag
combinations) so I inlined getopts.pl, and changed the comments, but left
the first part of the sentance -- the "if you have no getopts" was omitted.

SO: in brief do *NOT* add the "s" flag to the first line of brclient !

There are new versions of brloop and brclient which might cope better with
problems with the transatlantic link -- you should use brc0.09 and brl0.03

> anyway, i'm not sure i'll be participating this time as i won't be around 
> too much.

All the better -- your machine will have more cycles for CRACKing !
The purpose of SKSP is to make it work when you are not in ...


There is a "how to" page referenced from http://www.brute.cl.cam.ac.uk/brute/
which includes some "fault finding" tips.
If you have problems, look there first.
If that doesn't help, email me, and I'll add any "common" problems to the
"how to".





Thread