[RC5] win3.1 client (was Re: Re: Re: [RC5] Re:...)

Bob Jonkman bjonkman at sobac.com
Sat Jun 13 17:25:40 EDT 1998


I want to tell you what gindrup at okway.okstate.edu 
<rc5 at llamas.net> said about "Re[2]: [RC5] Re: win3.1 client " 
on 5 Jun 98, at 10:40

>      Of course, fetching and flushing to that client can be somewhat of a 
>      problem if you *only* run Win3.x machines...  I hear the beta client 
>      doesn't have this problem.
>             -- Eric Gindrup ! gindrup at okway.okstate.edu

The Win3x GUI client does bring up my Winsock dialler when 
first launched, which then dials up and stays connected 
forever.  The blocks now come and go automatically, but I 
can't afford infinite connect charges :-)

For those still using the DOS client there is e-mail fetching 
and flushing available (which announcement I take the liberty 
of attaching to this message for those who don't already know 
about it).

Version: 2.6.3i
Charset: cp850
Comment: PGP ensures message authenticity  and non-repudiability


Bob Jonkman                         SOBAC Microcomputer Services
4 Gold Pine Court                      mailto:bjonkman at sobac.com
Brampton  ON  L6S 2K6  Canada                Voice: 905-793-4537
Networking   --   Office & Business Automation   --   Consulting
Key fingerprint: 9F AF A6 AC B5 67 BC 10 89 73 7C F0 CB 27 03 17
Key ID: AE33E989      mailto:bjonkman at sobac.com?subject=send_key

-------------- next part --------------

Received: from chipsworld.llamas.net (majordom at chipsworld.llamas.net [])
	by xenon.xe.com (8.8.8/8.8.8) with ESMTP id FAA19766
	for <bjonkman at sobac.com>; Sat, 18 Apr 1998 05:16:24 -0400 (EDT)
Received: (from majordom at localhost)
	by chipsworld.llamas.net (8.8.8/8.8.8) id AAA10998
	for announce-outbound; Sat, 18 Apr 1998 00:40:53 -0400
Received: from watcher.highlander.org (imc6.sb.iit.edu [])
	by chipsworld.llamas.net (8.8.8/8.8.8) with ESMTP id AAA10995;
	Sat, 18 Apr 1998 00:40:48 -0400
Received: from localhost (beberg at localhost)
	by watcher.highlander.org (8.8.8/8.8.8) with SMTP id XAA24179;
	Fri, 17 Apr 1998 23:40:45 -0500
Date: Fri, 17 Apr 1998 23:40:44 -0500 (CDT)
From: "Adam L. Beberg" <beberg at distributed.net>
X-Sender: beberg at watcher.highlander.org
To: Undisclosed recipients:  ;
Subject: [ANNOUNCE] Email buffer flushing and fetching now available for RC5-64
Message-ID: <Pine.LNX.3.96.980417233647.23886A-100000 at watcher.highlander.org>
MIME-Version: 1.0
Sender: owner-announce at llamas.net
Precedence: bulk
Reply-To: rc5help at distributed.net
Content-Type: TEXT/PLAIN; charset=US-ASCII

Good news below, film at 11

- ---

You now have another method for flushing and fetching your RC5-64 buffers.
You may attach a buffer to be flushed to an email sent to
"flush at distributed.net", and the blocks will be flushed for you and a short
"receipt" sent back to you (Note: A lot of people have asked if this will
cause your blocks not to count on stats.. Not so. They will be credited to
you as usual.) You may also request buffers via email with
"fetch at distributed.net". We hope this will help people running clients where
access to a normal proxy is limited.
Here is a brief summary of how to use this new flush/fetch method:

To flush a buffer of completed blocks:

1) Create an email to "flush at distributed.net"
2) Attach your buffer to be flushed using either UUencoding or MIME Base64
encoding.  It must be called "buff-out.rc5"
3) Send the email

That's all there is to flushing. The blocks will be flushed to a personal
proxy, and you can view the statistics for the proxy at
http://www.interlog.com/~tcharron/myrc5home/ The pages are updated once a

To Fetch a buffer of new blocks:

1) Create and email to "fetch at distributed.net"
2) Determine the size of the blocks and buffers you need. The default is 100
blocks of 2^28 keys.
3) If you need a buffer of a different size, you can use the "blocksize=xx"
option to change the size of the blocks you will receive, and the
"numblocks=yyyy" to change the number of blocks you will receive. Simple
place the options anywhere in the body of your message. For example, to
retrieve a buffer of 250 block of 2^30 keys each, you would place the
following in the body of your message to "fetch at distributed.net":


blocksize may be an integer from 28 to 31, and numblocks may be an integer
from 0 to 1000.
4)Send your message. Your buffer will be mailed to you within a few hours.

A few things to remember:

1)The content of any messages sent to either "flush at distributed.net" or
"fetch at distributed.net" besides blocksize and numblocks commands will be
2)It may take some time for you to receive your buffers. Don't expect them
to return to you instantly.
3)Flushing by e-mail will not change your stats. The stats still recognize
the blocks as belonging to the person who's email is set in the client which
cracked them. If your client is set up with the email address
"johndoe at fakedomainname.com" the stats will attribute them to that e-mail
address, regardless of how they are flushed.

We hope you will find this new feature useful. Don't be afraid to ask for
help if you need it.


Jason White
a.k.a. Subground (subground at slacker.com)

- --
To unsubscribe, send 'unsubscribe announce' to majordomo at lists.distributed.net

Version: 2.6.3i
Charset: cp850
Comment: PGP ensures message authenticity  and non-repudiability


More information about the rc5 mailing list