Create challenge.yml

Author: Err0r417

OSINT/Blast-From-the-Past/challenge.yml

@@ -0,0 +1,98 @@
+# This file represents the base specification of your challenge. It is used by
+# other tools to install and deploy your challenge.
+
+# Required sections
+name: "Blast From the Past
+author: "Richie Joyce (Err0r417)"
+category: OSINT
+description: |
+  HELP! I've been sucked back to the 1900s at Penn State, and I can't get back. 
+  Oh well. If I'm here, may as well stay occupied. 
+  What club at Penn State is meeting at 102 Health and Human Development East on October 16, 1997?
+
+value: 35
+type: standard
+
+# The extra field provides additional fields for data during the install/sync commands/
+# Fields in extra can be used to supply additional information for other challenge types
+# For example the follow extra field is for dynamic challenges. To use these following
+# extra fields, set the type to "dynamic" and uncomment the "extra" section below
+# extra:
+#     initial: 500
+#     decay: 100
+#     minimum: 50
+
+# Settings used for Dockerfile deployment
+# If not used, remove or set to null
+# If you have a Dockerfile set to .
+# If you have an imaged hosted on Docker set to the image url (e.g. python/3.8:latest, registry.gitlab.com/python/3.8:latest)
+# Follow Docker best practices and assign a tag
+image: null
+# Specify a host to deploy the challenge onto.
+# The currently supported URI schemes are ssh:// and registry://
+# ssh is an ssh URI where the above image will be copied to and deployed (e.g. ssh://root@123.123.123.123)
+# registry is a Docker registry tag (e.g registry://registry.example.com/test/image)
+# host can also be specified during the deploy process: `ctf challenge deploy challenge --host=ssh://root@123.123.123.123`
+host: null
+
+# Optional settings
+
+# connection_info is used to provide a link, hostname, or instructions on how to connect to a challenge
+# connection_info: https://icespice-silly-ctf.psuccso.org/
+
+# healthcheck is a tool/script used to check a challenge
+# If connection_info was provided to CTFd when the challenge was installed, it will be passed to the healthcheck script:
+# ./writeup/exploit.sh --connection-info "nc hostname 12345"
+# healthcheck: writeup/exploit.sh
+
+# Can be removed if unused
+
+# Flags specify answers that your challenge use. You should generally provide at least one.
+# Can be removed if unused
+# Accepts strings or dictionaries of CTFd API data
+flags:
+    # A static case sensitive flag
+    - {
+        type: "static",
+        content: "CCSO{amnesty_international}",
+        data: "case_insensitive",
+    }
+    - {
+        type: "static",
+        content: "896160016",
+        data: "case_insensitive",
+    }
+# Topics are used to help tell what techniques/information a challenge involves
+# They are generally only visible to admins
+# Accepts strings
+#topics:
+#    - icespice
+
+# Tags are used to provide additional public tagging to a challenge
+# Can be removed if unused
+# Accepts strings
+tags:
+    - OSINT
+    - Medium
+
+# Provide paths to files from the same directory that this file is in
+# Accepts strings
+
+# Hints are used to give players a way to buy or have suggestions. They are not
+# required but can be nice.
+# Can be removed if unused
+# Accepts dictionaries or strings
+#hints:
+    - {
+        content: "You may have to go WAAAAAY back...",
+        cost: 5
+    }
+
+# The state of the challenge.
+# If the field is omitted, the challenge is visible by default.
+# If provided, the field can take one of two values: hidden, visible.
+state: visible
+
+# Specifies what version of the challenge specification was used.
+# Subject to change until ctfcli v1.0.0
+version: "0.1"