7.0.6

Changes:

• isort formatting

Full Changelog: 7.0.5...7.0.6

7.0.5

Changes:

• Remove instances of Optional and Union
• black formatting

Full Changelog: 7.0.4...7.0.5

7.0.4

Changes:

• PEP 585
• black formatting
• bump pick to 2.y.z

Full Changelog: 7.0.3...7.0.4

7.0.3

Changes:

• Improve pyproject.toml to prevent adding unwanted files to distributed package

Full Changelog: 7.0.2...7.0.3

7.0.2

Changes:

• Migrate to pyproject.toml only

Full Changelog: 7.0.1...7.0.2

7.0.1

Changes:

• Fix setup script

Don't forget to look at 7.0.0 major changes.

Full Changelog: 7.0.0...7.0.1

7.0.0

Breaking changes:

• configuration file structure slightly changed
• major refactoring in package structure and library API
• templates changed to reflect changes of the library API

Other Changes:

• black is used to format source code
• rich replaces termcolor
• uses dataclasses and typing
• mkctf-server was removed because it was not production ready nor useful
• project packaging as a proper Python package
• setup script updated

License Change: project is now licensed under MIT license.

Unchanged:

• core concepts: Repository and Challenge remain almost identical even if renamed to RepositoryAPI and ChallengeAPI
• dashboard HTTP API: /mkctf-api/push and /mkctf-api/healthcheck endpoints remain the same
• standard challenge scripts: program invocation and exit code interpretation remain the same

Full Changelog: 6.0.1...7.0.0

mkCTF v6.0.0

Changelog

Enhancements described in issues (#6, #7, #9 and #10) have been implemented.

• Massive refactoring (better separation between the CLI and the API)
• Add author to challenges metadata
• mkctf-monitor and monitoring files to build a Docker image
• Introduction of categories (from the infrastructure point of view)
• Generate challenge files from jinja templates (including full scripts)

Warning

Major changes have been made regarding configuration files and their location. Some path are now harcoded to ensure more stability between releases.

Old versions of mkCTF can only be ported manually. The easiest way to do that is to:

1. Install version 6.0.0 of mkCTF,
2. create a new repository,
3. copy all challenges from the old repository to the new one in challenges/ directory,
4. fix each challenge configuration file (.mkctf.yml) by:
   • adding author key and set a string as the value
   • removing parameters key
   • renaming standalone key to category and set a value comprised in {simple, server, sandbox}
   • renaming the company_logo_url key to logo_url
5. rename exploit/exploit to healthcheck/healthcheck

And that should be ok. I've not tested it though.

mkCTF v4.0.0

Changes

• Model update to match INS'hAck 2019 requirements.
• Fix mkctf/util/cli.py : isdigit() check which did not allow negative integers.

Warning

mkCTF files generated with an older version must be patched manually to be compatible with this new release.

mkCTF v3.0.0

Code has been refactored and MKCTFAPI is now the central class.

It offers functions used by both CLI and WebAPI scripts.