Skip to content

Releases: picoCTF/cmgr

Release v2.0.0

06 May 14:53
v2.0.0
d2753f1
Compare
Choose a tag to compare

Changes

  • Challenge types other than remote-make and static-make are no longer supported.
    • Existing challenges of other types can be converted to custom by exporting their Dockerfile (cmgr dockerfile <type>).
  • JSON challenge specifications (problem.json) are no longer supported. Any existing challenges using this format must be converted to use problem.md instead.

Release v1.2.1

12 Feb 18:07
v1.2.1
a1f38d7
Compare
Choose a tag to compare

Changes

  • Fixed an issue preventing ARM64 builds in GitHub release artifacts from working correctly.
  • Linux ARM64 builds are no longer available.

Release v1.2.0

30 Jan 02:16
Compare
Choose a tag to compare

Changes

  • The cmgr update-schema command and POST /schemas/{schema_name} cmgrd endpoint now function as upserts: if the specified schema does not yet exist, a warning is logged and it is created. This allows clients to easily apply updates to schemas without needing to consider whether they already exist (ca62a57)

Release v1.1.1

29 Jan 18:00
v1.1.1
50de11d
Compare
Choose a tag to compare

Changes

  • Fixes bugs related to the use of {{url}} and {{lookup}} templates in the Description field, as introduced in v1.1.0 (50de11d)

Release v1.1.0

26 Jan 04:29
v1.1.0
2eefb47
Compare
Choose a tag to compare

Changes

  • {{url}}, {{url_for}}, and {{lookup}} templates are now permitted in the Description section (2eefb47).
    The primary motivation is to allow players to download artifacts prior to launching instances of on-demand challenges.

Release v1.0.0

19 Jan 06:11
v1.0.0
96df299
Compare
Choose a tag to compare

Changes

  • Updated seccomp profile to fix syscall issues in newer base images (c93ebcf)
  • Reverted to cgo-based SQLite driver due to issues with concurrent transactions (0f6bee8)
  • Added labels to challenge instance containers (e3e839e):
    • cmgr.managed=true for all challenge instances
    • cmgr.dynamic=<bool> depending on whether the instance is of a build with instance_count: -1