Rename custom service to reversing python

Author: syreal17

dev-advice.md

@@ -54,7 +54,7 @@
     [problem.md](https://github.com/picoCTF/start-problem-dev/blob/master/example-problems/sanity-static-flag/problem.md?plain=1#L24)
 - When writing custom Dockerfiles, reference base images by SHA to avoid drift
   - See this
-    [Dockerfile](https://github.com/picoCTF/start-problem-dev/blob/master/example-problems/custom-service/Dockerfile#L1)
+    [Dockerfile](https://github.com/picoCTF/start-problem-dev/blob/master/example-problems/reversing-python/Dockerfile#L1)
 
 ## Challenge Accessibility
 

example-problems/README.md

@@ -16,7 +16,7 @@ problem development with.
 1. [Web CSS](/example-problems/web-css/)
    - Demonstrates hosting a simple nginx-based web problem. Also introduces
      configuring the container with a Python script.
-1. [Custom Service](/example-problems/custom-service/)
+1. [Reversing Python](/example-problems/reversing-python/)
    - Presents a vulnerable program through a port using socat. Also goes over
      some tips on debugging your Dockerfile.
 1. [Custom SSH (Multi-stage Dockerfile)](/example-problems/custom-ssh/)

example-problems/custom-ssh/README.md

@@ -5,11 +5,11 @@
 1. You have `cmgr` installed and configured.
     - Refer to the [setup page](/setup-cmgr) if this is not the case for you.
 
-2. You have done the [Custom Service Problem Creation
-   Walkthrough](/example-problems/custom-service/). The Custom Service
+2. You have done the [Reversing Python Problem Creation
+   Walkthrough](/example-problems/reversing-python/). The Reversing Python
    walkthrough is a more basic example of using a custom Dockerfile for cmgr
    problem development. The file changes presented here will be as compared to
-   Custom Service.
+   Reversing Python.
 
 ## Overview
 
@@ -62,7 +62,7 @@ be separate containers, not just secure permissions.
    container. "builder" is actually a special name to cmgr, it's the container
    that it always expects to find `/challenge/metadata.json` and
    `/challenge/artifacts.tar.gz` if applicable. The rest of "builder" is
-   similar to Custom Service. "sshHost" isn't too different either, but notice
+   similar to Reversing Python. "sshHost" isn't too different either, but notice
    the COPY instructions that grab files from "builder", such as line 40. This
    is a critical ability to connect your containers and your other containers
    are likely to need to know things from the "builder" container. We copy all

example-problems/custom-service/.gitignore renamed to example-problems/reversing-python/.gitignore

@@ -1,4 +1,4 @@
-# Custom Service Problem Creation Walkthrough
+# Reversing Python Problem Creation Walkthrough
 
 ## Pre-requisites
 
@@ -37,23 +37,23 @@ This problem is adapted from the live picoGym problem, `Picker-I`.
 ### File Listing
 
 1. Besides problem details, the most important change in
-   [problem.md](/example-problems/custom-service/problem.md) is changing Type
+   [problem.md](/example-problems/reversing-python/problem.md) is changing Type
    to "custom".
 
-1. [picker-I.py](/example-problems/custom-service/picker-I.py) this is the
+1. [picker-I.py](/example-problems/reversing-python/picker-I.py) this is the
    vulnerable script that we will be hosting as a service on this container.
 
-1. [start.sh](/example-problems/custom-service/start.sh) starts a listener that
+1. [start.sh](/example-problems/reversing-python/start.sh) starts a listener that
    receives connections. This script is ran as the last step in the
    Dockerfile. For this problem, we use socat to connect the output of our
    vulnerable script to a port, allowing users to interact with our script
    through the network.
 
-1. [setup-challenge.py](/example-problems/custom-service/setup-challenge.py)
+1. [setup-challenge.py](/example-problems/reversing-python/setup-challenge.py)
    This script generates the flag for the problem and saves it in the important
    file, `/challenge/metadata.json`, which is required for every cmgr problem.
 
-1. [Dockerfile](/example-problems/custom-service/Dockerfile) this is the main
+1. [Dockerfile](/example-problems/reversing-python/Dockerfile) this is the main
    setup for our problem. We pull down a pinned Ubuntu image, update it and
    install the required packages. We create the `/challenge` directory with
    specific permissions so only root can access it. `/challenge` is an
@@ -74,13 +74,13 @@ process goes a long way in being able to determine what is going wrong.
 
 1. Clone this repo
 2. Go to the custom-ssh directory
-    - `cd start-problem-dev/example-problems/custom-service/`
+    - `cd start-problem-dev/example-problems/reversing-python/`
 3. Switch Dockerfiles. `Dockerfile.test` has 1 discrepancy in it.
     - `mv Dockerfile Dockerfile.good`
     - `mv Dockerfile.test Dockerfile`
 4. Build the problem with cmgr
       - `cmgr update`
-      - `cmgr playtest picoctf/custom-service`
+      - `cmgr playtest picoctf/examples/reversing-python`
       - Expected output:
 
          ```terminal

example-problems/custom-service/Dockerfile renamed to example-problems/reversing-python/Dockerfile

@@ -1,7 +1,7 @@
-# Custom-Service
+# Reversing Python
 
 - Namespace: picoctf/examples
-- ID: custom-service
+- ID: reversing-python
 - Type: custom
 - Category: Reverse Engineering
 - Points: 100

example-problems/custom-service/Dockerfile.test renamed to example-problems/reversing-python/Dockerfile.test

@@ -71,5 +71,5 @@ nginx as a base image. This allowed us to use custom HTML and CSS very simply in
 order to hide the flag in one of these files. We used Python to configure this
 container which leads to a cleaner implementation.
 
-[Next problem](/example-problems/custom-service)
+[Next problem](/example-problems/reversing-python)
 [Return to the index](/example-problems#example-problems)