staff blogs

distributed.net staff keep (relatively) up-to-date logs of their activities in .plan files. These were traditionally available via finger, but we've put them on the web for easier consumption.

2002-09-25

distributed.net completes rc5-64 project (list announcement)

Filed under: project status — Tags: @ 00:00 +00:00

RC5-64 HAS BEEN SOLVED!

On 14-Jul-2002, a relatively characterless PIII-450 in Tokyo returned the winning key to the distributed.net keyservers. The key 0x63DE7DC154F4D039 produces the plaintext output:

The unknown message is: some things are better left unread

Unfortunately, due to breakage in scripts (dbaker’s fault, naturally) on the keymaster, this successful submission was not automatically detected. It sat undiscovered until 12-Aug-2002. The key was immediately submitted to RSA Labs and was verified as the winning key.

So, after 1,757 days and 58,747,597,657 work units tested the winning key was found! While it’s debatable that the duration of this project does much to devalue the security of a 64-bit RC5 key by much, we can say with confidence that RC5-64 is not an appropriate algorithm to use for data that will still be sensitive in more than several years’ time. On the distributed computing front, however, the RC5-64 project clearly demonstrates the viability of long-term, volunteer-driven, internet-based collaborative efforts. The next time someone bemoans the public’s short attention span or need for instant gratification you should remind them what 331,252 people were able to accomplish by joining together and working for nearly five years. distributed.net’s RC5-64 project clearly shows that even the most ambitious projects can be completed by volunteers thanks to the combined power of the internet and distributed computing.

Ignoring artificially high numbers resulting from network difficulties, we completed 86,950,894 workunits on our best day. This is 0.12% of the total keyspace meaning that at our peak rate we could expect to exhaust the keyspace in 790 days. Our peak rate of 270,147,024 kkeys/sec is equivalent to 32,504 800MHz Apple PowerBook G4 laptops or 45,998 2GHz AMD Athlon XP machines or (to use some rc5-56 numbers) nearly a half million Pentium Pro 200s.

Over the course of the RC5-64 project, 331,252 individuals participated. We tested 15,769,938,165,961,326,592 keys.

We apologize for the latency in the announcement, but scheduling conflicts with RSA Laboratories and difficulties in reaching the winning participant (who has asked to remain anonymous) introduced the additional delay to the process.

Also, please consider joining us on SlashNET IRC on Saturday 28-Sep-2002 @ 21:00 UTC (5:00PM EDT) for an online Q+A session on the RC5-64 project and the future plans for the distributed.net network. Not only are we looking forward to moving on to RC5-72 but we’re currently reshaping the framework of the dnetc architecture to better accommodate additional projects. We’re hoping to attract some new and motivated partners with good ideas and a need for cycles.

Thanks to RSA Labs for continuing to offer challenges that reward distributed efforts!

For more information, contact:
* David McNett <nugget@distributed.net> +1-512-350-5038

References

http://www.slashnet.org/
http://www.rsasecurity.com/news/releases/pr.asp?doc_id=1400
http://www.distributed.net/rc5/

2002-08-11

bovine [11-Aug-2002 @ 22:51]

Filed under: Uncategorized @ 22:51 +00:00

:: 11-Aug-2002 22:51 GMT (Sunday) ::

Just thought I’d share some interesting statistics and graphs that I
dug up for RC5-64 right now.

The following graph shows the overall “return rates” that we have
obtained for subspaces 90 through 135, for their most recent recycled
distribution passes.
http://www1.distributed.net/~bovine/elapsed-return-rate-20020811.png

This represents work that was sent out between Jun/26/2002 through
today (we are currently on 135 right now). The horizontal axis
represents elapsed time between when a workunit is sent out and when
the result is received back, and each data point represents a
different subspace.

Although the data is a little noisy (the trend should ideally be
strictly increasing), the trends are still quite observable. As you
can see, a majority of our participants seems to return blocks back
after about 4 days, with relatively negligible results anytime
afterwards. Additionally, every time we send a workunit out on a new
recycle pass, only about 75% of those are ever actually returned (most
likely because people fetch more blocks than they intended and delete
the excess).

Here is another potentially interesting graph that shows the current
completion percentages for all 256 subspaces.
http://www1.distributed.net/~bovine/subspace-complete-20020811.png

As a reminder, the overall percent complete across the entire keyspace
is about 85%; this is the same number that is shown on the statsbox at
http://stats.distributed.net/projects.php?project_id=5

2002-08-06

bovine [06-Aug-2002 @ 08:49]

Filed under: Uncategorized @ 08:49 +00:00

:: 06-Aug-2002 08:49 GMT (Tuesday) ::

I’ve made available some new pre-release clients (v2.8019.473) for the
following platforms:

* amigaos-ppc-pup
* amigaos-ppc-wos
* dos-x86
* linux-x86-elf
* netbsd-mipsel
* openbsd-sparc-aout
* openbsd-x86-aout
* ps2linux-mips
* win16-x86
* win32-x86-setup
* win32-x86

You can find download links for these new clients under
http://www.distributed.net/download/prerelease.html
There are a few important changes made in this new version:

* fix: static: rebuilt all static clients to fix CA-2002-19:
“Buffer Overflow in Multiple DNS Resolver Libraries”
* chg: all: increased buff-in.* limit to 2000 packets
* imp: x86: improved P4 RC5 core (ak-p7) (#2542)
* new: x86: detect latest Pentium III (#2778) and Athlon XP (#2783)
* chg: linux: enable /proc/apm support for non-x86 (#2643)
* fix: all: processed RC5 random blocks even if RC5 was disabled
* fix: amigaos: fixed problems with font requester opening in
GUI prefs window when clicking other gadgets
* imp: amigaos: can be shutdown by pressing escape key in GUI

2002-07-19

bovine [19-Jul-2002 @ 17:16]

Filed under: Uncategorized @ 17:16 +00:00

:: 19-Jul-2002 17:16 GMT (Friday) ::

Some users have reported DNS problems sometimes resolving addresses
under *.v27.distributed.net or *.proxy.distributed.net, because one of
our (several) secondary DNS servers was not properly syncing. The
ability to resolve such addresses would depend on which of our DNS
servers your machine happened to quasi-randomly select. It is now
believed that this problem has been corrected (subject to the timeouts
of your local DNS servers caching negative responses).

2002-06-08

bovine [08-Jun-2002 @ 01:26]

Filed under: Uncategorized @ 01:26 +00:00

:: 08-Jun-2002 01:26 GMT (Saturday) ::

Moose updated some new clients on June 3rd on the pre-release download
page, at http://www.distributed.net/download/prerelease.html The
updated clients include:

* Win32 [x86/Zipped] v2.8018.472b 2002-06-03
* Win32 [x86/Setup] v2.8018.472b 2002-06-03
* Windows 3.x [x86] v2.8018.472b 2002-06-03
* PC-DOS, MS-DOS [x86] v2.8018.472b 2002-06-03
* Linux [x86/ELF] v2.8018.472b 2002-06-03
* Linux [mips/PS2] v2.8018.472b 2002-06-03

This week there have been some routing issues with our two keyservers
in Redwood City, CA (proxy1.rwc.ca.us.proxy.distributed.net and
proxy2.rwc.ca.us.proxy.distributed.net). There is a large backlog of
blocks sitting on both of these machines, which accounts for why some
participant stats may have been low this week. The routing issue
appears to be fixed now, but it may take a day or so for everything to
get caught up again.

I’ve also just relocated my distributed.net photo gallery, from under
my personal web space, to a more officially named virtual host. You
can now find these pictures (of primarily distributed.net staff and
other miscellaneous images) under http://gallery.distributed.net/

2002-04-12

bovine [12-Apr-2002 @ 16:00]

Filed under: Uncategorized @ 16:00 +00:00

:: 12-Apr-2002 16:00 GMT (Friday) ::

If you’re looking for something to do while idling and waiting for the
keymaster to be relocated to its new location, then you may like to
take the time to wish a happy birthday to both Moonwick
and Daa . Most
significantly, it’s Moonie’s 21st birthday today and there are some
awesome party plans scheduled for him tonight! ]:8)

2002-03-31

bovine [31-Mar-2002 @ 21:24]

Filed under: Uncategorized @ 21:24 +00:00

:: 31-Mar-2002 21:24 GMT (Sunday) ::

Hopefully the plan mailing list should again be working, after
rewriting the several hundred lines of Perl that drive the checking
and formation of the mails. Included in the rewrite were some
additional safety checks to eliminate the occasional mishaps that
caused old plan files to sometimes be mistakenly emailed out.

2002-03-23

bovine [23-Mar-2002 @ 08:33]

Filed under: Uncategorized @ 08:33 +00:00

:: 23-Mar-2002 08:33 GMT (Saturday) ::

The keymaster relocation was completed a couple hours ago and a number
of the public fullservers have already begun catching up. There are
still a few of our keyservers that have not yet been redirected to the
new keymaster, but it is expected that all of them should be updated
within the next dozen hours or so.

Although you should not need to take any direct action for any of your
dnetc clients to eventually recover, you can monitor the progress by
looking at the number of servers not shown in red on this status page:

http://n0cgi.distributed.net/rc5-proxyinfo.html

2002-03-22

bovine [22-Mar-2002 @ 17:02]

Filed under: Uncategorized @ 17:02 +00:00

:: 22-Mar-2002 17:02 GMT (Friday) ::

There may be some increased backlog within the proxy network today
starting in a couple of hours. We will be relocating the central
keymaster to another location. irc.distributed.net will also suffer
some lack of connectivity between the nodes, since the central IRC hub
will also be relocated at the same time. Some DNS queries to the
*.distributed.net domain may be delayed, since one of the DNS
secondaries is also affected.

2002-03-20

bovine [20-Mar-2002 @ 22:46]

Filed under: Uncategorized @ 22:46 +00:00

:: 20-Mar-2002 22:46 GMT (Wednesday) ::

Network connectivity should be improving now for most people. There
may be slight delays because of the resulting traffic spike.

« Newer PostsOlder Posts »