Ctfreak - Package Updates
-
[1.20.1]
- Update ctfreak to 1.30.1
- Full Changelog
-
[1.20.2]
- Update ctfreak to 1.30.2
-
[1.21.0]
- Update ctfreak to 1.31.0
-
[1.22.0]
- Update ctfreak to 1.32.0
- Full Changelog
- A task can use multiple notifiers: For example, for a given task, you can now both send a Slack notification each time it executes, but only create a Jira issue on failed execution.
- API Breaking change: Reading/creating/updating tasks (for all fields related to notifiers)
- API Breaking change: Reading task reports (removal of all fields relating to notifiers)
- Mask the password when updating a password credential
-
[1.23.0]
- Update ctfreak to 1.33.0
- Full Changelog
- Add SOVEREIGN Edition license for fully air-gapped CTFreak instance, with license validation based on hardware fingerprinting rather than online checking
- In Email notifiers, there is an option to ignore the SSL certificate when connecting to the SMTP server.
- Back-end is built with Go 1.25.5
- Update dependencies
- Fix spinner animation
- Fix regression preventing the password from being saved on email notifier creation
- Fix minor memory leak
-
[1.24.0]
- Update ctfreak to 1.34.0
- Full Changelog
- The list of nodes and databases that can be used by project tasks can now be restricted at the project level
-
[1.25.0]
- Update ctfreak to 1.35.0
- Full Changelog
-
[1.26.0]
- Update ctfreak to 1.36.1
- Full Changelog
- Personal Access Tokens: generate personal access tokens to authenticate API calls without using the OAuth token endpoint, facilitating integration of CTFreak with third-party tools such as Zabbix
- Add GitLab notifier to automatically create a GitLab issue on execution failure
- Add Ntfy notifier to send alerting notifications to a ntfy topic
- Add Gitea and Forgejo incoming webhook types with signature verification
-
[1.27.0]
- Update ctfreak to 1.37.0
- Full Changelog
-
[1.28.0]
- Update ctfreak to 1.38.0
- Full Changelog
- Secret encryption: sensitive fields (credentials, API tokens, webhook secrets, OIDC client secrets, SMTP passwords, license key) can be encrypted with AES-256-GCM in the backend database (BUSINESS Edition licence or higher is required)
- Ntfy integration is now defined at the project level (service URL and access token), aligning with other third-party integrations (GitHub, Jira, Linear, etc.)
- Memory allocation optimizations for list retrievals
- License compatibility checks now distinguish between backend database incompatibility and encryption type incompatibility
Hello! It looks like you're interested in this conversation, but you don't have an account yet.
Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.
With your input, this post could be even better 💗
Register Login