`custom-socat` challenge is broken because of incorrect port mapping

ArmyCyberInstitute / cmgr

CTF Challenge Manager

Apache License 2.0

18 stars 9 forks source link

`custom-socat` challenge is broken because of incorrect port mapping #52

Open codders opened 1 year ago

codders commented 1 year ago

For the custom-socat puzzle to be solvable, the listening port in the docker container needs to be exposed to the world. Currently socat in the container listens on 4242, and the port exposed via docker / cmgr is mapper to 4200

codders commented 1 year ago

Opened #53 to address this