Distributed.net OGR is back up

[Jeff McCright]

Randy Rathbun,

I assume that I need a broadband internet connection(DSL/Cable modem)?
Also, what is the URL again and what team are you on? I assume the KCLUG?

Thanks,

Jeff McCright
jeff.mccright at southernunionco.com
 ----------
From: kclug at kclug.org
To: kclug at kclug.org
Cc: jeff.mccright at southernunionco.com
Subject: Re: kclug - Distributed.net OGR is back up

Okay, the first thing you need to do is let it do some stuff for a 24 hour
period at least. Make sure you have your email address in the dnet client
so you get credit for your work!

Once it is cracking/OGRing, go to stats.distributed.net. Check your email
address in the OGR stats (or RC5 stats) and there is a thing to mail you
your password. Get that password, then edit your profile.

Go back to the stats and search for the word "kansas". You will see three
(last time I checked, anyway) groups with the word Kansas in
them... Kansas City Linux Users Group, Kansas City 2600, and some team in
Arkansas. Select KCLUG and down at the bottom is a thing that says
something like "I want to join this team".

If you have any questions, be sure to ask! Will be more than happy to
help.

On Mon, 31 Jul 2000, Charles Mallahan Jr. wrote:

> I have the distributed.net set up and configured on my Windoze machine, and gunzipped and untar'd 
on the linux
> box, but cant get it configured and running.  Any help would be appriciated.  How do I credit my 
work to the
> kclug?  I searched the whole site for joining.
>
> Jeff McCright wrote:
>
> > Having never participated in an Encryption Crack project/contest,
> > what is required and how does one join in on it? How would I go about "adding machine cycles" 
to the task?
> >
> > Thanks,
> >
> > Jeff McCright
> > jeff.mccright at southernunionco.com
> >  ----------
> > From: kclug at kclug.org
> > To: kclug at kclug.org
> > Cc: jeff.mccright at southernunionco.com
> > Subject: Re: kclug - Distributed.net OGR is back up
> > Date: Friday, July 28, 2000 1:15PM
> >
> > > The more that are crunching, the sooner you will not have to
> > > put up with my "join the dnet team!" messages.  :)
> >
> > or you could do what i just did: put together a little procmail
> > recipe to send future messages on this subject to /dev/null.
> >
> > phase
> >
>
>
>
>
>
>