Change custom-ssh to general-ssh

Author: syreal17

example-problems/README.md

@@ -19,7 +19,7 @@ problem development with.
 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/)
+1. [General SSH (Multi-container)](/example-problems/general-ssh/)
    - Demonstrates separating the challenge builder container from the
      interactive container.
 

example-problems/custom-ssh/.gitignore renamed to example-problems/general-ssh/.gitignore

@@ -1,4 +1,4 @@
-# Custom SSH Problem Creation Walkthrough
+# General SSH Problem Creation Walkthrough
 
 ## Pre-requisites
 
@@ -19,7 +19,7 @@ the filesystem that together compose the flag.
 The new thing about this challenge is that it uses multiple build stages in the
 Dockerfile to make use of multiple containers instead of just one.
 
-In Custom SSH, we spin up an Ubuntu container called "builder" and use it to
+In General SSH, we spin up an Ubuntu container called "builder" and use it to
 make the flag and store it in separate files and in `/challenge/metadata.json`.
 We spin up another container which we call "sshHost". This is the container
 that becomes the main focal point of the challenge. We copy the separate parts
@@ -37,23 +37,23 @@ be separate containers, not just secure permissions.
 ### File Listing
 
 1. Besides problem details, the most important change in
-   [problem.md](/example-problems/custom-ssh/problem.md) is changing Type to
+   [problem.md](/example-problems/general-ssh/problem.md) is changing Type to
    "custom".
 
 2. instructions-to-Xof3.txt's contain verbal instructions on how to find the
    next part of the flag. The Dockerfile copies these into the "sshHost"
    container.
 
-3. [profile](/example-problems/custom-ssh/profile) is a bash profile that
+3. [profile](/example-problems/general-ssh/profile) is a bash profile that
    places the newly logged in user into a different folder than their home
    directory. This is done so that returning home from the root directory
    yields the last part of the flag instead of the first.
 
-4. [start.sh](/example-problems/custom-ssh/start.sh) starts a listener that
+4. [start.sh](/example-problems/general-ssh/start.sh) starts a listener that
    receives ssh connections. This script is ran as the last step in the
    Dockerfile.
 
-5. [Dockerfile](/example-problems/custom-ssh/Dockerfile), the first line is
+5. [Dockerfile](/example-problems/general-ssh/Dockerfile), the first line is
    different for this file. It's the "LAUNCH" directive which tells cmgr which
    containers should be actively running for the challenge. For our challenge,
    we don't need "builder" running, but we do need "sshHost" running. The next
@@ -69,15 +69,15 @@ be separate containers, not just secure permissions.
    of the flag parts in the Dockerfile since it can access them easily with
    `COPY --from=builder ...`.
 
-6. [config-builder.py](/example-problems/custom-ssh/config-builder.py), this
+6. [config-builder.py](/example-problems/general-ssh/config-builder.py), this
    script generates the password from the seed and puts it in the file for the
    "sshHost" to use. Then it generates the flag and splits it into 3 parts and
    writes a file for each, also for the "sshHost" container. Finally, it writes
    the whole flag into `/challenge/metadata.json`, as needed by cmgr. It also
    puts the "password" into this file, so that the problem description can give
    the password to the competitor.
 
-7. [config-sshhost.py](/example-problems/custom-ssh/config-sshhost.py), this
+7. [config-sshhost.py](/example-problems/general-ssh/config-sshhost.py), this
    script creates the "ctf-player" user and the needed directories and also
    changes the password of the account to be that which was generated by the
    "builder" container.

example-problems/custom-ssh/Dockerfile renamed to example-problems/general-ssh/Dockerfile

@@ -1,5 +1,5 @@
 ################################################################################
-# Configure a box for the custom ssh example challenge.
+# Configure a box for the general ssh example challenge.
 ################################################################################
 
 

example-problems/custom-ssh/Dockerfile.test renamed to example-problems/general-ssh/Dockerfile.test

@@ -1,5 +1,5 @@
 ################################################################################
-# Configure a box for the custom ssh example challenge.
+# Configure a box for the general ssh example challenge.
 ################################################################################
 
 

example-problems/custom-ssh/README.md renamed to example-problems/general-ssh/README.md

@@ -1,7 +1,7 @@
-# Custom SSH
+# General SSH
 
 - Namespace: picoctf/examples
-- ID: custom-ssh
+- ID: general-ssh
 - Type: custom
 - Category: General Skills
 - Points: 1
@@ -11,6 +11,7 @@
 Do you know how to move between directories and read files in the shell?
 
 ## Details
+
 `ssh -p {{port("ssh")}} ctf-player@{{server("ssh")}}` using password 
 `{{lookup("password")}}`
 

example-problems/custom-ssh/config-builder.py renamed to example-problems/general-ssh/config-builder.py

@@ -73,7 +73,7 @@ the cmgr user, and some more control and introspection of the docker build
 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
+2. Go to the reversing-python directory
     - `cd start-problem-dev/example-problems/reversing-python/`
 3. Switch Dockerfiles. `Dockerfile.test` has 1 discrepancy in it.
     - `mv Dockerfile Dockerfile.good`

example-problems/custom-ssh/config-sshhost.py renamed to example-problems/general-ssh/config-sshhost.py

@@ -57,11 +57,11 @@ our previous implementation of using sed in a Dockerfile will fail silently.
 Python is also helpful for writing `metadata.json`. Even writing one line for
 the flag is clunky using `echo` in the Dockerfile. Doing this is much cleaner
 in Python, and necessary if we end up writing more variables than just the flag,
-such as in this [config](/example-problems/custom-ssh/config-builder.py#L70).
+such as in this [config](/example-problems/general-ssh/config-builder.py#L70).
 
 Everything that can be done in the Dockerfile, can be done in Python, though
 usually more verbosely, but with better error handling and friendlier syntax.
-Here's an [example](/example-problems/custom-ssh/config-sshhost.py#L24) of
+Here's an [example](/example-problems/general-ssh/config-sshhost.py#L24) of
 running an arbitrary shell command in Python.
 
 ## Conclusion