Back to Top
To register for the contest and be eligible to win, several things must happen.
They do not need to happen all at the same time. You can pre-register now and
receive the hashes as soon as the contest starts, or do so during the
Detailed instructions for each step are below.
Import our PGP keys
There are two PGP keys you need to import:
Submitting your PGP key
- The key for firstname.lastname@example.org, the submission
autoresponder, available here.
That's the email address and PGP key you'll use for all the
- The key for email@example.com, the group alias
for the humans running the contest, available
here. You really only need this if
something goes wrong, and you need to contact us (or we contact
you; our correspondence will always be signed).
You can use an existing PGP key or create a new one--however, the one
you use *must* have only one UID (email address), so don't use an existing
key if you have multiple UIDs attached to it.
You must send us the key in an email that is encrypted to us and signed
by that key. You do *not* have to send all mails to us From: the email
address in the key, *but* you must be able to *receive* emails sent to
that address. I.e. if firstname.lastname@example.org and email@example.com create a
PGP key for firstname.lastname@example.org, it is fine if all their mails to us come from
either alice@ or bob@ or wherever, as long as they will receive replies
we send to email@example.com.
You may use ASCII-armored, inline PGP messages or MIME messages with
PGP'ed attachments (either sign+encrypt the whole message, or add a
signed & encrypted attachment to a plaintext message).
A suitable way to compose your key-registration email
after you've made your key using GnuPG would look like this, assuming
your new PGP key has keyid 0xDEADBEEF:
$ gpg -a -o my-key.pub.asc --export DEADBEEF
$ gpg -a -o keysub-email.asc -r firstname.lastname@example.org \
And then either email that as an inline-PGP message:
$ mail -s "PGP key" email@example.com < keysub-email.asc
Or attach the file keysub-email.asc to an email to
firstname.lastname@example.org, such as if you are using Gmail.
The Subject: is not really important, nor is the From: - we only trust
what is inside the encrypted+signed message.
Don't forget to add '--default-key DEADBEEF' if you have more than one
secret key, such as if you created one just for use during this contest.
When we have learned your PGP key, we will send a
challenge to the email address in the PGP key. This is to make sure we
are able to reach you at that address and using that key. Once you
decrypt that, it will have instructions on what to send back to us to
confirm your address. When we receive and verify that response from
you, you will get another email acknowledging it. Your email address
will be on the list to receive the password hashes, and to submit
cracked passwords to us. However you will not be eligible to
win, nor will your team's activity be published on the stats page, until
we have received a registration code from you to prove that someone from
your team attended DEFCON (see below).
Your primary identifier, as far as we are concerned, is your PGP keyid.
Team names are sugar for the stats page, etc.
Team names must be from 4 to 40 characters long, and consist of only
letters, numbers, spaces, hyphens, and underscores, and start and end
with a letter or number. In other words, they must match:
We reserve the right to reject or mangle your submitted name.
Register your team name with us by sending a signed, encrypted email
as described above, containing the line:
...in the encrypted body. You can include this when you are first sending
us your key; just include the Team: line as the first line of the payload,
followed by the PGP public key block, that you encrypt into keysub-email.asc in
the example above.
We will notify you (after you've confirmed your email address; see
above) if we reject your team name for some reason (duplicate, contained
nothing but profanity, etc). In the meantime your team will be identified
by its PGP keyid.
Registration Code (at DEFCON)
All of the steps above can be done before you've physically arrived
at DEFCON. You can (and we recommend you do) submit your PGP key and
team name, and answer the confirmation challenge in advance.
Once you have submitted your PGP key and confirmed its email address,
you can start participating in the contest. (So, if you are not arriving
at DEFCON until late Friday, you can still start cracking at midnight
with everybody else.) But you will not be eligible to win unless
you complete the final step, submitting a valid registration code.
At our table at DEFCON, we will be handing out little pieces of paper
with registration codes on them. Come visit us, get a registration
code, and then send us an encrypted, signed email containing the line:
If you have not pre-registered your PGP key, you can do all three
steps something like this:
$ echo "Team: awesome" > reg-email
$ echo "Code: 1A2B-3C4D-5E6F-7081" >> reg-email
$ gpg -a --export DEADBEEF >> reg-email
$ gpg -a -o keysub-email.asc -r email@example.com \
$ mail -s "Registration" firstname.lastname@example.org \
(Again, remember --default-key DEADBEEF if this isn't your only key.)
After this you will still need to wait for the challenge, decrypt and
respond to it.
Now go on to submitting cracks.