distributed.net

(Redirected from Dnetc)

Distributed.net is a volunteer computing effort that is attempting to solve large scale problems using otherwise idle CPU or GPU time. It is governed by Distributed Computing Technologies, Incorporated (DCTI), a non-profit organization under U.S. tax code 501(c)(3).

distributed.net
The distributed.net logo
Type of site
Volunteer computing
OwnerDistributed Computing Technologies, Inc.
URLdistributed.net
LaunchedFebruary 1997
Current statusActive

Distributed.net is working on RC5-72 (breaking RC5 with a 72-bit key).[1] The RC5-72 project is on pace to exhaust the keyspace in just over 40 years as of February 2024,[2] although the project will end whenever the required key is found. RC5 has eight unsolved challenges from RSA Security, although in May 2007, RSA Security announced[3] that they would no longer be providing prize money for a correct key to any of their secret key challenges. distributed.net has decided to sponsor the original prize offer for finding the key as a result.[4]

In 2001, distributed.net was estimated to have a throughput of over 30 TFLOPS.[5] As of August 2019, the throughput was estimated to be the same as a Cray XC40, as used in the Lonestar 5 supercomputer,[6] or around 1.25 petaFLOPs.[7]

History

edit

A coordinated effort was started in February 1997 by Earle Ady and Christopher G. Stach II of Hotjobs.com and New Media Labs, as an effort to break the RC5-56 portion of the RSA Secret-Key Challenge, a 56-bit encryption algorithm that had a $10,000 USD prize available to anyone who could find the key. Unfortunately, this initial effort had to be suspended as the result of SYN flood attacks by participants upon the server.[8]

A new independent effort, named distributed.net, was coordinated by Jeffrey A. Lawson, Adam L. Beberg, and David C. McNett along with several others who would serve on the board and operate infrastructure. By late March 1997 new proxies were released to resume RC5-56 and work began on enhanced clients. A cow head was selected as the icon of the application and the project's mascot.[9]

The RC5-56 challenge was solved on October 19, 1997 after 250 days. The correct key was "0x532B744CC20999" and the plaintext message read "The unknown message is: It's time to move to a longer key length".[10]

The RC5-64 challenge was solved on July 14, 2002 after 1,757 days. The correct key was "0x63DE7DC154F4D039" and the plaintext message read "The unknown message is: Some things are better left unread".[11]

The search for Optimal Golomb Rulers (OGRs) of order 24, 25, 26, 27 and 28 were completed by distributed.net on 13 October 2004, 25 October 2008, 24 February 2009, 19 February 2014, and 23 November 2022 respectively.[12][13][14][15][16]

Client

edit

"DNETC" is the file name of the software application which users run to participate in any active distributed.net project. It is a command line program with an interface to configure it, available for a wide variety of platforms.[17] distributed.net refers to the software application simply as the "client". As of April 2019, volunteers running 32-bit Windows with AMD FireStream enabled GPUs have contributed the most processing power to the RC5-72 project[18] and volunteers running 64-bit Linux have contributed the most processing power to the OGR-28 project.[19]

Portions of the source code for the client are publicly available, although users are not permitted to distribute modified versions themselves.[20]

Distributed.net's RC5-72 project is available on the BOINC client through the Moo! Wrapper.[21]

Development of GPU-enabled clients

edit
 
Average daily RC5-72 production by platform for 2 February 2024 – 27 May 2024[22]

In recent years, most of the work on the RC5-72 project has been submitted by clients that run on the GPU of modern graphics cards. Although the project had already been underway for almost 6 years when the first GPUs began submitting results, as of May 2024, GPUs represent 88% of all completed work units,[23] and complete more than 95% of all work units each day.[22]

  • NVIDIA
In late 2007, work began on the implementation of new RC5-72 cores designed to run on NVIDIA CUDA-enabled hardware, with the first completed work units reported in November 2008. On high-end NVIDIA video cards at the time, upwards of 600 million keys/second was observed[24] For comparison, a 2008-era high-end single CPU working on RC5-72 achieved about 50 million keys/second, representing a very significant advancement for RC5-72. As of May 2024, CUDA clients have completed 11% of all work on the RC5-72 project, and performs about 10% of the work each day.[23]
  • AMD / ATI
Similarly, near the end of 2008, work began on the implementation of new RC5-72 cores designed to run on AMD FireStream-enabled hardware. Some of the products in the Radeon HD 5000 and 6000 series provided key rates in excess of 1.8 billion keys/second.[25] As of May 2024, FireStream clients have completed over 23% of all work on the RC5-72 project.[23] Daily production from FireStream clients has dropped below 0.5% as the majority of AMD GPU contributors now use the OpenCL client.[23]
  • OpenCL
An OpenCL client entered beta testing in late 2012 and was released in 2013. As of May 2024, OpenCL clients have completed more than 53% of all work on the RC5-72 project, and now performs about 85% of the work each day. No breakdown of OpenCL production by GPU manufacturer exists, as AMD, NVIDIA, and Intel GPUs all support OpenCL.[26]

Timeline of distributed.net projects

edit
Timeline of projects hosted by distributed.net, as of February 2024
Current
  • RSA Lab's 72-bit RC5 Encryption Challenge started 3 December 2002 — In progress, 12.613% complete as of 20 September 2024[27] (although RSA Labs has discontinued sponsorship)
Cryptography
  • RSA Lab's 56-bit RC5 Encryption Challenge — Completed 19 October 1997 (after 250 days and 47% of the key space tested).
  • RSA Lab's 56-bit DES-II-1 Encryption Challenge — Completed 23 February 1998 (after 39 days)[28]
  • RSA Lab's 56-bit DES-II-2 Encryption Challenge — Ended 15 July 1998 (found independently by the EFF DES cracker after 2.5 days)[29]
  • RSA Lab's 56-bit DES-III Encryption Challenge — Completed 19 January 1999 (after 22.5 hours with the help of the EFF DES cracker)
  • CS-Cipher Challenge — Completed 16 January 2000 (after 60 days and 98% of the key space tested).[30]
  • RSA Lab's 64-bit RC5 Encryption Challenge — Completed 14 July 2002 (after 1726 days and 83% of the key space tested).[31]
Golomb rulers
  • Optimal Golomb Rulers (OGR-24) — Completed 13 October 2004[32] (after 1552 days, confirmed predicted best ruler)
  • Optimal Golomb Rulers (OGR-25) — Completed 24 October 2008[33] (after 3006 days, confirmed predicted best ruler)
  • Optimal Golomb Rulers (OGR-26) — Completed 24 February 2009[34] (after 121 days, confirmed predicted best ruler)
  • Optimal Golomb Rulers (OGR-27) — Completed 19 February 2014[35] (after 1822 days, confirmed predicted best ruler)
  • Optimal Golomb Rulers (OGR-28) — Completed 23 November 2022[36] (after 3199 days, confirmed predicted best ruler)

See also

edit

References

edit
  1. ^ "RC5-72 project page". distributed.net.
  2. ^ "RC5-72 / Overall Project Stats". rsa.com. Archived from the original on 2023-09-17.
  3. ^ "RSA Laboratories Secret-Key Challenge". rsa.com. Archived from the original on 2007-07-06.
  4. ^ "RC5-72 Continuation Announcement". distributed.net.
  5. ^ "distributed.net mailing list archive".
  6. ^ "Distributed.net: Staff blogs – 2019 – August – 23".
  7. ^ "TACC's Lonestar 5 Supercomputer Now in Full Production".
  8. ^ Glave, James (1997-03-03). "Macho Computing at Root of RSA Contest Flap". Wired.
  9. ^ "What's with all the cows?". distributed.net.
  10. ^ "distributed.net: Project RC5". www.distributed.net. Retrieved 2019-04-23.
  11. ^ "distributed.net: Project RC5". www.distributed.net. Retrieved 2019-04-23.
  12. ^ "distributed.net: staff blogs – 2004 – November – 01". Retrieved 2019-04-23.
  13. ^ "distributed.net: staff blogs – 2008 – October – 25". Retrieved 2019-04-23.
  14. ^ "distributed.net: staff blogs – 2009 – February – 24". Retrieved 2019-04-23.
  15. ^ "distributed.net: staff blogs – 2014 – February – 25". Retrieved 2019-04-23.
  16. ^ "distributed.net: staff blogs – 2022 – November – 23". Retrieved 2022-12-29.
  17. ^ "distributed.net: Client Downloads". www.distributed.net. Retrieved 2019-04-22.
  18. ^ "stats.distributed.net - RC5-72 CPU Participation". stats.distributed.net. Retrieved 2019-04-23.
  19. ^ "stats.distributed.net - OGR-28 CPU Participation". stats.distributed.net. Retrieved 2019-04-23.
  20. ^ "Public source code". distributed.net. Archived from the original on 2012-05-23. Retrieved 2010-01-23.
  21. ^ "Moo! Wrapper". Moo! Wrapper. Retrieved 2019-03-08.
  22. ^ a b Calculated by subtracting the completed work units as of 27 May 2024 from the totals on 2 February 2024, creating a 115-day average.
  23. ^ a b c d "RC5-72 / CPU Participation". distributed.net. Retrieved 27 May 2023.
  24. ^ "Client Speeds Database (GPU RC5-72 search)". distributed.net. Retrieved 27 February 2014.
  25. ^ "Benchmark results for Radeon HD 5870". MrJackson2000. April 1, 2010.
  26. ^ "[TEST] GPU Computing - GeForce and Radeon OpenCL Test (Part 3) | Geeks3D". 2010-01-16. Retrieved 2023-09-05.
  27. ^ "RC5-72 Overall Project Stats". distributed.net. Retrieved 20 September 2024.
  28. ^ David C. McNett (24 February 1998). "The secret message is..." distributed.net. Archived from the original on 4 March 2016. Retrieved 27 February 2014.
  29. ^ "The Electronic Frontier Foundation DES Cracker FAQ". EFF. 16 July 1998. Archived from the original on 7 May 2017. Retrieved 27 February 2014.
  30. ^ "CSC project page". distributed.net. 16 January 2000. Retrieved 25 February 2016.
  31. ^ "History & Timeline". distributed.net.
  32. ^ "distributed.net is proud to announce the completion of OGR-24!". 2004-11-01.
  33. ^ "distributed.net is proud to announce the completion of OGR-25!". 2008-10-25.
  34. ^ "Howdy all". 2009-02-24.
  35. ^ "OGR-27 Completion Announcement". 2014-02-25.
  36. ^ "Completion of OGR-28 project". 2022-11-23.
edit