Contest Submisson Format
An example of a submission follows:
solution: 23 3e ef 79 a4 85 c7 f2
name: Julius Caesar and Brutus
address: Julius Caesar
time: Around 10,000 MIPS-years
method: Two people using abacuses
Note: All submissions will receive an automated reply from RSA acknowledging it has been received and winners will be notfiied from RSA some time thereafter.
All submissions of a candidate secret key for any of the contests must be sent by email to email@example.com. A submission should contain (in the message body) a number of fields specifying information such as which contest the submission is being made for, the name(s) of the person or people making the submission, the actual key value being submitted, and other relevant information. Each field has a field header, followed by a colon, followed by the value of the field. After all the fields, there must be a line containing just the string "done:", to indicate the end of the submission.
Solutions should be presented in hexadecimal, as shown. If the solution is for the DES then the parity bits of the key must be set as specified in the U.S. Federal Standard FIPS 46-2.
The "challenge", "solution", "name", "address", "email", and "phone" fields are required to be present in every submission. Without these fields the submission will be rejected. The other fields, "time" and "method", are not required but RSA Laboratories would very much like them to be present for any information they might reveal. While the MIPS-year (the amount of computation completed in a year by a machine operating at the rate of 1,000,000 instructions per second) is the most conventional unit for measuring computing power, it is not always easy to rate the machine(s) being used in terms of MIPS-years. In such cases we would like to receive as much detail as possible with regards to the type of machine being used and the estimated amount of time spent on the search problem (including the fraction of that time actually spent working on the problem at hand, if the search was conducted as part of a background process).
Fields can be contained in more than one line, like the "address" field in the example. However, each field must start on a new line. The "address", "email", and "phone" fields should contain only one address, email address, and phone number, respectively.