RC5 is 3 months away

[Joe O]

from its 5th anniversary!

Your thoughts please.

 

[EagleKeeper]

Will never see 6th b-day

 

[Adul]

will never see another wu from me

 

[IJump]

will get to 100% without finding the key

 

[Evadman]

Originally posted by: IJump
will get to 100% without finding the key

I say 138%

 

[networkman]

will get to 100% without finding the key

Yep, I'm thinking that too.

 

[IJump]

Originally posted by: Evadman

Originally posted by: IJump
will get to 100% without finding the key

I say 138%

Maybe I should say "or higher"

 

[Postman]

Well atleast RC5 has measurable progress and concrete goal..

 

[Baldy18]

Will start recieving blocks from me as of yesterday. Lets get this dang thing over with and hold our #2 ranking.

 

[MWalkden]

Am looking for a network monitoing replacement for when they find the key, but no hurry!

Actually the key has randomly changed itself using only available keyspace to regenerate, It does this when it detects that the keyserver is within 50,000 blocks of distributing it and it is a bug in the keyserver not yet discovered! (J/K)

Ok, so the odds that the key has been found already are better than the odds of finding it (for anyone!)!

Where does it leave all us RC5 junkies?

CRACKIN ANYWAY!!!!

I know our next project: Determine how long RC5 blocks will keep comming into DNET after the project is finished! Unless a proactive stance is taken to have clients removed from systems still crunchin away that the RC5 random stream will continue for nearly 10 years beyond the end of the project.



What you think?

.(MW)

 

[Joe O]

MW you bring up a good point! What will happen to all those machines if the network is shut down? Will they continue to try to connect? Will they clog themselves with random results? Will Distributed.NET help to track them all down? Do they have a special block that will shut them all down?

 

[Wolfie]

Originally posted by: Baldy18
Will start recieving blocks from me as of yesterday. Lets get this dang thing over with and hold our #2 ranking.

I agree... Lets get this thing over with and lets climb back to at least #2 for output a day...


Wolfie

 

[JonB]

Joe O, I think there is a key that can turn the client off, just like they used to switch you automatically from one contest to another. There was also the method of putting a "shutdown" file into the same directory as the client, but that isn't practical for anybody except personal herds.

I have put most of my UD clients on hold for a few weeks/months. I want to be in on finishing this to 100%.

If it goes past 100%, I will not continue. That is a possibility, especially with a lot of the hacking attempts by teams a few years ago (remember the big Russian team fiasco?). I have no trouble believing that it is in the last 17% of keys. My biggest problem is that keyspace is SO FRAGMENTED, I can't get any big blocks anymore. They are all 2's and 4's and 6's in size now.

My PProxy buffers just don't last very long for my sneakernet machines and the "expertmode" switch doesn't seem to work.

 

[Joe O]

JonB, I hope that they haven't lost the turn off key too! <G>
I remember the "Russian scandal". I thought that they subtracted those blocks from the "done" count when they banished that particular team.
Do you remember the "bad client" that they pulled? AFAIK they haven't re checked those blocks yet. I was looking for a breakdown by client similar to what the proxies do, but couldn't find it.
I wonder if they will "fess up" and tell us up front how many blocks need to be rechecked?

 

[ViRGE]

Joe, the problem with the whole Russian fiasco is that they're only people we know did it. It's very possible that there are other people/teams that are cheating, but haven't been discovered. If that's the case, we may have passed up the key because of it, and never know it until we do find it with another search.

 

[LANMAN]

Originally posted by: EagleKeeper
Will never see 6th b-day

Thats fine with me; the more people we can get over to SETI!!

--LANMAN

 

[kranky]

LOL @ Evadman's "138%" comment!

Maybe dnet could make sure the correct key is somewhere in the remaining keyspace just to avoid going over 100%.

JonB, lack of big blocks is a real PITA for me too as I have to use email to move pproxy buffers around. I usually fetch work about once a week and if the blocks are small it takes forever. But last week fate smiled on me and I got about 80,000 blocks worth of huge blocks. So don't give up hope.

 

[ViRGE]

Kranky, I don't think anyone, not even RSA, knows what the key is. Obviously, RSA knows the message, but I remember reading somewhere that no one knows what the key is. Hopefully, I'm wrong.

 

[Joe O]

Here's another possibility. The "winning" key has already been returned, but not announced. Distributed.net wants to see how long an exhaustive search will take, i.e. how long to 100%.

 

[JonB]

Joe O, I think that last one is remote. At this point, they can extrapolate the endpoint with 2 to 5 day accuracy. The backlash against other DNET or United Devices projects would be too great a risk.

We'll see how lucky Team Anandtech is during this last part of the contest. My daughter is now 1 of 100 students who get to pick a key for a new VW Beetle. Maybe we can get lucky on the same day (Aug 17th).

 

[SpaceWalker]

All I know is that as soon as RC5 is done, I'm switching my systems to SETI...

 

[Baldy18]

I'm now up to somewhere between 6-7GHz running RC5 which is really hurting my SETI production. I have to do my part though to get Spacewalker doing SETI as soon as possible.

I would like ot find the RC5 key but I would also like to get lucky in the mikeshardlemonade.com drawing on Aug. 7 and win a motor cycle.