Skip to content

Releases: google/kctf

Release 1.4.0

14 Jan 16:05
Compare
Choose a tag to compare

Changes since 1.3.4:

  • Additional MacOS Compatibility by @jeffg2k
  • Upgrade operator-framework to 1.x so kCTF is compatible with Kubernetes 1.22

Important: Upgrading the operator on an existing cluster requires deleting the old operator through:

kubectl delete kctf-operator -n kctf-system

Full Changelog: v1.3.4...v1.4.0

Release 1.3.4

29 Oct 08:59
56a94bb
Compare
Choose a tag to compare

Changes since 1.3.3:

  • faster pow with gmp
  • fix a bug in the xss-bot healthcheck where the webserver would not reply (contributed by phiber)
  • fix the dns setup since gcloud format changed
  • make kctf scripts compatible with macos (contributed by jeffg2k)

Release 1.3.3

09 Jul 19:42
f4093ac
Compare
Choose a tag to compare

gcsfuse upgrade had a backwards-incompatible change

Release 1.3.2

09 Jul 15:57
71aa83a
Compare
Choose a tag to compare

bugfix: the gcsfuse change didn't make it into the operator due to a bug in the github workflow

Release 1.3.1

09 Jul 14:40
4eed77e
Compare
Choose a tag to compare

Upgrade gcsfuse to latest (better logging)

Release 1.3.0

08 Jul 11:06
43f168b
Compare
Choose a tag to compare

New feature:

  • support additional objects in challenge.yaml (separated by ---)

Other changes:

  • default pwn nsjail template is a bit easier to use
  • make command errors more visible
  • fix an operator panic if there are non-kctf deployments
  • print stderr of gcloud in some cases where it might require reauth
  • fixed the example in the readme of the web chal template

Release 1.2.1

05 Jul 12:46
daa584f
Compare
Choose a tag to compare

Bugfixes:

  • dns zone names would break if the domain started with a digit. Fixed by prepending kctf-
  • kind cluster would not start with newer kernels, update kind version
  • use unbuffered stdin for proof-of-work
  • allow overwriting the healthcheck probe configuration

Release 1.2.0

01 Jul 12:35
45b84fc
Compare
Choose a tag to compare

New feature:
HTTPS ports now have a new field: domains
You can specify additional domains to get certificates for. Make sure to set up the proper CNAME entry first (see docs).

Release 1.1.0

29 Jun 08:26
6a59222
Compare
Choose a tag to compare

New feature release!
You can now add ranges of IPs that are allowed to connect to your challenges.
This can be useful for private testing.

Use kctf cluster set-src-ip-ranges to configure the list.

Release 1.0.8

24 Jun 08:12
12160df
Compare
Choose a tag to compare

A bugfix to stop overwriting the security context of the challenge container if specified by the challenge author.