I won't have have to worry about running out of entropy, I'm going to have my OTP generated forever with this new script!

Connect at nc socket.cryptohack.org 13372

Challenge files:
  - 13372.py

You must be logged in to submit your flag.

Each time you connect, I generate a new one time pad. I also check for leaks, so there's no chance you can learn anything about my secrets!

Connect at nc socket.cryptohack.org 13370

Challenge files:
  - 13370.py

You must be logged in to submit your flag.

I'm opening a virtual casino and this is my first game. It's all luck-based and biased towards the house so I'll be a multi-millionaire in no time.

Connect at nc socket.cryptohack.org 13383

Challenge files:
  - 13383.py

You must be logged in to submit your flag.

My first casino game was a big hit, but there was an issue with the RNG. Some players cheated and others thought it wasn't fair. This time I've picked a better RNG from a cryptographic standard, and I'm mixing in some lucky numbers chosen by the players so that everyone is happy.

Connect at nc socket.cryptohack.org 13387

Challenge files:
  - 13387.py

You must be logged in to submit your flag.

Here's a new fast way I've found for generating RSA keys for smart cards.

Challenge files:
  - rsa-vs-rng.py
  - flag.enc


Challenge contributed by jschnei

You must be logged in to submit your flag.

Following the issues with our casino games, we're testing a stronger random number generator. Can you win our trust by finding an attack on our latest model?

Connect at nc socket.cryptohack.org 13396

Challenge files:
  - 13396.py


Challenge contributed by $in

You must be logged in to submit your flag.

Can you recover the input for a simple Linear Feedback Shift Register with unknown taps?

Challenge files:
  - lwin.py
  - output.txt


Challenge contributed by Cryptanalyse

You must be logged in to submit your flag.

Jeff heard that LFSRs used as stream ciphers aren't very secure, so he combined three LFSRs together. Foolproof, right?

Challenge files:
  - jeff.py
  - output.txt


Challenge contributed by Cryptanalyse

You must be logged in to submit your flag.

You are well on your way to mastering LFSRs if you can crack this. Hurry, your time is limited!

Connect at nc socket.cryptohack.org 13404

Challenge files:
  - 13404.py


Challenge contributed by Cryptanalyse

You must be logged in to submit your flag.

I heard ElGamal has some cool properties. I've encrypted every bit with a different secret, so you'll never recover my flag.

Challenge files:
  - source.py
  - output.txt

You must be logged in to submit your flag.

Here's my improvement on Shamir's scheme with deterministically derived shares. Great for storing Bitcoin private keys and other secret data.
You've only got the first share and you need 3 to unlock the flag so you have no chance.

Challenge files:
  - armory.py
  - share.txt

You must be logged in to submit your flag.

You are hyperreality and you are playing an online treasure hunt with your team mpeg, codecrafting, RichGirlOnLSD and pogo.

There's one million dollars in a Bitcoin wallet - which nobody yet knows the address for - awaiting the first team to gain 5 of 6 SSSS shares and combine them to a private key. Each member of your team has found one share and you're ready to do the key ceremony to unlock the prize.

The SSSS implementation is simply the example code on Wikipedia, with the 13th Mersenne prime. The server will tell you your share in the first message.

You've all agreed to split the million dollars equally, however in a final moment of greed you decide you want it all for yourself!

Here's your evil plan:

1. Disrupt the first combination by submitting a fake share. The others assume a mistake was made and try again.

2. This time, submit a fake share such that the combined secret is a private key for a wallet that you own containing just $1k. This will confuse your teammates and make them think they have been cheated by the game creators, not you.

3. Unlock the real wallet and use the funds to escape to an island nation where nobody will ever be able to find you.

Connect at nc socket.cryptohack.org 13384

Challenge files:
  - hyper_privkey.txt

You must be logged in to submit your flag.

https://www.schneierfacts.com/facts/842

The challenge server is running 64-bit Linux, which might explain if you are seeing different results locally.

Connect at nc socket.cryptohack.org 13400

Challenge files:
  - 13400.py


Challenge contributed by esrever

You must be logged in to submit your flag.

Bruce Schneier's password was too easy to Bruce-force, so some Schneiertational complexity was added.

Connect at nc socket.cryptohack.org 13401

Challenge files:
  - 13401.py


Challenge contributed by esrever

You must be logged in to submit your flag.