- Oct 9, 1999
- 31,516
- 167
- 106
At the moment, Dnet(The operator of RC5) has not 1, but 2 projects going. The first and main project is obviously RC5, but they also have another project called OGR going on right now that differs in several ways from RC5.
Whereas RC5 is a contest to decrypt a 64bit RC5 message, it's also being used as a way to test Dnet's method of Distributed Computing. Now that they've more or less done that, they've launched their first true scientific project, Optimal Golomb Ruler(OGR). In a nutshell, OGR is a contest to try to find the shortest integer ruler possible, where no 2 marks are the same distance apart. These optimal rulers can be used for X-ray crystallography and radio astronomy as their main points, but have also been used as cryptography methods and communications, which is why OGR is Dnet's scientific project.
OGR has all the benefits that RC5 has(stats, easy to use client, ect), and only differs in the project type. OGR is cracked by the same client that RC5 is, and for that reason only requires a reconfiguration if the client is version v2.8009.460 or later(any version past that needs to be updated). It also has the benefit of being newer than RC5, which means people who've been at it from the beginning have less of a lead than in RC5.
Now, there are 2 ways you can do OGR, either by itself(replacing RC5), or in tandem with RC5.
1) To do OGR by itself, go into the configuration menu, then type 2(Buffer and buffer update options) and then 9(Load-work precedence). From there, clear the "settings" line, and replace it with the following:
OGR,RC5=0,DES=0,CSC=0
Then press "enter" to save this new setting, then "0" twice to exit the configuration screen and save any new settings. This will tell the client to do only OGR, and it will start on it after the client restarts.
2) To do OGR in tandem with RC5(where it cracks some RC5 blocks, then some OGR stubs, then updates and starts the process again) get into the proper configuration screen as show in #1, but use the following line instead:
RC5,OGR,DES=0,CSC=0
However, you next will probably want to modify your WU settings, so that you have less RC5 and OGR work units, as the time between buffer updates will be longer, due to both projects running. As a rule of thumb, a single OGR stub will be larger than the smallest RC5 WU(2^28), so you should hold less OGR stubs than RC5 blocks to keep things balanced.
After you've done all of that, save your new settings, and let the client restart. It'll finish off its RC5 WUs, start OGR, and go through the cycle again after it finishes the OGR stubs.
-----
After you've done the above, you're done. Since you're already on Team Anandtech RC5, all OGR stubs cracked by you count for TA automatically, and the same profile is used for you both in RC5 and OGR, so there's no need for a new password, user number, ect.
So, welcome to Team Anandtech OGR. Hopefully, you can help us beat everyone just as quickly as we've been doing it in RC5!
Whereas RC5 is a contest to decrypt a 64bit RC5 message, it's also being used as a way to test Dnet's method of Distributed Computing. Now that they've more or less done that, they've launched their first true scientific project, Optimal Golomb Ruler(OGR). In a nutshell, OGR is a contest to try to find the shortest integer ruler possible, where no 2 marks are the same distance apart. These optimal rulers can be used for X-ray crystallography and radio astronomy as their main points, but have also been used as cryptography methods and communications, which is why OGR is Dnet's scientific project.
OGR has all the benefits that RC5 has(stats, easy to use client, ect), and only differs in the project type. OGR is cracked by the same client that RC5 is, and for that reason only requires a reconfiguration if the client is version v2.8009.460 or later(any version past that needs to be updated). It also has the benefit of being newer than RC5, which means people who've been at it from the beginning have less of a lead than in RC5.
Now, there are 2 ways you can do OGR, either by itself(replacing RC5), or in tandem with RC5.
1) To do OGR by itself, go into the configuration menu, then type 2(Buffer and buffer update options) and then 9(Load-work precedence). From there, clear the "settings" line, and replace it with the following:
OGR,RC5=0,DES=0,CSC=0
Then press "enter" to save this new setting, then "0" twice to exit the configuration screen and save any new settings. This will tell the client to do only OGR, and it will start on it after the client restarts.
2) To do OGR in tandem with RC5(where it cracks some RC5 blocks, then some OGR stubs, then updates and starts the process again) get into the proper configuration screen as show in #1, but use the following line instead:
RC5,OGR,DES=0,CSC=0
However, you next will probably want to modify your WU settings, so that you have less RC5 and OGR work units, as the time between buffer updates will be longer, due to both projects running. As a rule of thumb, a single OGR stub will be larger than the smallest RC5 WU(2^28), so you should hold less OGR stubs than RC5 blocks to keep things balanced.
After you've done all of that, save your new settings, and let the client restart. It'll finish off its RC5 WUs, start OGR, and go through the cycle again after it finishes the OGR stubs.
-----
After you've done the above, you're done. Since you're already on Team Anandtech RC5, all OGR stubs cracked by you count for TA automatically, and the same profile is used for you both in RC5 and OGR, so there's no need for a new password, user number, ect.
So, welcome to Team Anandtech OGR. Hopefully, you can help us beat everyone just as quickly as we've been doing it in RC5!
Facebook
Twitter