cryptoanarchy.wiki

Arise, you have nothing to lose but your barbed wire fences!

1995-08-24 - Re: brloop not working

Header Data

From: Thomas Grant Edwards <tedwards@src.umd.edu>
To: Piete Brooks <Piete.Brooks@cl.cam.ac.uk>
Message Hash: e028886ad3bec384e9e5baeb00a0d2d0f2effca6c6725ad1b502feb899f2b961
Message ID: <Pine.SUN.3.91.950824172624.22646F-100000@thrash.src.umd.edu>
Reply To: <“swan.cl.cam.:150900:950824172806”@cl.cam.ac.uk>
UTC Datetime: 1995-08-24 21:35:56 UTC
Raw Date: Thu, 24 Aug 95 14:35:56 PDT

Raw message

From: Thomas Grant Edwards <tedwards@src.umd.edu>
Date: Thu, 24 Aug 95 14:35:56 PDT
To: Piete Brooks <Piete.Brooks@cl.cam.ac.uk>
Subject: Re: brloop not working
In-Reply-To: <"swan.cl.cam.:150900:950824172806"@cl.cam.ac.uk>
Message-ID: <Pine.SUN.3.91.950824172624.22646F-100000@thrash.src.umd.edu>
MIME-Version: 1.0
Content-Type: text/plain


On Thu, 24 Aug 1995, Piete Brooks wrote:

> The first arg of brutessl is the file from which to read the config info.
> "-" is a unix convention for the file "stdin".

OK - I dig this, but brutessl on my Linux box is still complaining about 
usage...(sorry about the bandwidth but I assume other people are probably 
having similar problems)

+ eval brclient -dklLtssl|(read a;nice -20 brutessl - $a)|(read a;echo  
$a 1>&2;
 echo $a) |brclient -AlLtssl
++ brclient -dklLtssl
++ brclient -AlLtssl
++ read a
++ read a
++ nice -20 brutessl -
usage: brutessl [-q] <filename> <checksum> <start segment> <no of 
segments>
       brutessl [-q] -r <filename> [<no of segments>]
       brutessl [-q] -t [<hours>[:<minutes>]]

-Thomas

Thread