Sign inSign up

detee/hacker-challenge

By detee

•Updated over 1 year ago

DeTEE Hacker Challenge Node

Image
Security
Web servers
0

518

detee/hacker-challenge repository overview

⁠DeTEE Hacker Challenge Node

Visit documentation⁠ for more details.

Warning

Hacker challenge is licensed under GPLv2⁠.
To participate in the Hacker Challenge, you must agree with following:

  • I acknowledge that I will not be able to recover any cryptocurrencies that I send to the Hacker Challenge wallet, and I am relinquishing ownership rights to any cryptocurrencies sent to the Hacker Challenge wallet.
  • I acknowledge that the tokens minted by the Hacker Challenge have no inherent value, and that these tokens have the sole purpose of testing the security of the challenge.
  • I have read the EULA⁠ and I accept all terms.

⁠Prerequisites

For running the Hacker Challenge you need a VM with Intel processor that supports SGX1/2, check supported processors⁠. You may also rent a VM, see RedSwitches⁠ or Hetzner⁠. Public IP is not mandatory to participate.

Make sure you enabled SGX in BIOS. Just do cpuid | grep SGX to see if SGX is enabled. Make sure you also have kernel above v5.13 to get a built-in SGX DCAP driver. Final step is to add the symlinks for the sgx devices.

sudo mkdir -p /dev/sgx
sudo ln -sf ../sgx_enclave /dev/sgx/enclave
sudo ln -sf ../sgx_provision /dev/sgx/provision

⁠Quick Start

Hacker challenge works as a cluster that anybody can join. To join a cluster you need to run the DeTEE Hacker Challenge node (for simplicity we call it dthc):

docker run --device /dev/sgx/enclave --device /dev/sgx/provision --env INIT_NODES="212.95.45.139 46.165.199.12 184.107.183.210" -v /tmp/dthc:/challenge/main -p 80:31372 -p 31373:31373 -d  --name dthc detee/hacker-challenge:latest

After your node has started, feel free to start exploring logs in docker logs <hash> and in /tmp/dthc/logs

  • devices are mandatory to give node the access to the SGX driver
  • INIT_NODES are current nodes (we update them) so that your node can download Solana keys from cluster
  • in the /tmp/dthc you will find the file where the node writes Solana keys, it's called TRY_TO_HACK_THIS
  • port 31373 is needed if you have a public IP and want other nodes to connect to you
  • port 80 is the web interface of your node, it has /nodes, /metrics and /mint?address=... endpoints

Tag summary

Content type

Image

Digest

sha256:1f29fbd9d…

Size

103.3 MB

Last updated

over 1 year ago

docker pull detee/hacker-challenge