venus/CTF-tool
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

coming allong nicely. adding more commands, tests, and

Browse Source 
artifacts for testing. basic framework down just adding features now
This commit is contained in:
venus
2026-07-18 02:38:13 -05:00
parent 8274d08f3e
commit 4dc0a24152
15 changed files with 362 additions and 209 deletions
Download Patch File Download Diff File Expand all files Collapse all files

20
project_status.md
View File

@@ -19,13 +19,17 @@ This file tracks the completed progress and upcoming development milestones for
## Upcoming Milestones & Features
### 📅 Phase 1: Configuration Completion & Basic File Scraper
* Extend [config.toml](file:///home/venus/code/ctf/config.toml) to store arbitrary data in the future
* Implement a basic tool to load the latest download files into the active directory
### 📅 Phase 1: Functional Forensics Pipeline & Toolkit
* **Pipeline Automation**: Integrate the existing forensics command-line utilities into a cohesive analysis pipeline where files are automatically checked for magic bytes, file extensions, and flag patterns.
* **Metadata & Extraction Toolkit**: Extend forensics tools to extract specific metadata (e.g., EXIF records, archive tables) and automate extraction/carving of nested data structures (e.g., binwalk-like carving, automated unzipping, extraction of hidden payloads).
* **QOL Utilities**: Add standard format outputs (JSON, Rich logs) and automatic logging of analysis artifacts to speed up user-led inspections.
### 📅 Phase 2: Downloads Organizer & Progress Tracker
* Write a tool to scan specified download directories for newly acquired challenge files and automatically organize them into the active competition's directory structure.
* Implement progress tracking to output current exploration paths, notes, and milestones.
### 📅 Phase 2: Core CTF Solving & Solver QOL
* **Challenge Organization**: Implement automated download management, challenge creation, directory configuration, and context management (`set-challenge`).
* **Solving Assistants**: Build automated helper scripts for common solving needs (e.g., basic cryptography decoders, web request templates, PSK cracking utility integration).
* **Solve Tracker & Note-taking QOL**: Create a command-line interface to capture solver actions, record active notes, log flag attempts, and update challenge statuses.
* **Per-Challenge Progress Logging**: Design a challenge-specific progress logger that creates and maintains isolated log files for each active challenge in a specified workspace directory, tracking attempts, timestamps, solver notes, and command history.
### 📅 Phase 3: Forensics Metadata Expansion
* Extend forensics tools to parse specific file-format metadata (e.g. EXIF data for JPGs or headers for specific archives).
### 📅 Phase 3: Agentic Solving Capabilities
* **Sandbox Environments**: Prepare secure, isolated environments to run untrusted challenge scripts or binaries.
* **Agent Orchestration**: Equip the toolchain with LLM agents capable of viewing the forensics pipeline outputs, reading challenge text, suggesting next steps, executing terminal tools, and recursively working to solve the challenge autonomously.