Agebox

Abstract

1. Introduction

Have you ever thought _"this should be simple"_ while you were using tools like [Blackbox] , [Git-crypt] or [Sops]? This is what agebox is. A tool on top of [Age]'s security system that encrypts/decrypts your repository files, focused on simplicity and gitops.

Easy and simple file repository encryption tool based on [Age].

2. Objective

Age based repository file encryption gitops tool

This project demonstrates how Go can be applied to a real-world Cybersecurity & Ethical Hacking problem.

3. Key Features / Modules

• Secure (Agebox delegates security to [Age]).
• Tracks encrypted files in repository.
• No PGP and no agents, just simple SSH and [Age] key files.
• File flexibility (encrypts/decrypts recursive paths, multiple/single files, all tracked files...).
• Reencrypts all tracked files with a single command.
• Focused on Gitops, CI flows and simplicity.
• Works with any file (doesn't understand formats like JSON, YAML...).
• Single binary/executable.
• No side effects like VCS commands (e.g: doesn't execute Git commands for you).

4. Technology Stack

5. System Requirements

General requirements for this technology stack — check the README for exact versions.

• Go 1.20 or later
• Git (to clone the repository)

6. Installation & Setup

git clone https://github.com/slok/agebox.git
cd agebox

agebox init

agebox encrypt ./app1/secret1.yaml ./app2/secret1.yaml

agebox encrypt ./secrets --dry-run

agebox encrypt ./manifests --filter ".*secret(\.yaml|\.yml)$"

Full setup instructions are in the project README.

7. Future Enhancements

Suggested extensions you can add to make this your own project.

• Add logging and alert notifications (email / Telegram)
• Write a threat model document for the tool
• Package it with Docker for safe lab testing

8. Viva / Review Questions

Common questions examiners ask for projects in this domain.

1. Which threat or attack does this project defend against?
2. What detection or protection technique is used and what are its limits?
3. How are false positives and false negatives handled?
4. Which cryptographic algorithms or security standards are involved?
5. What legal and ethical rules apply when testing a tool like this?

9. Source Code & License

This project is developed by slok and published on GitHub under the Apache License 2.0. Please follow the license terms and credit the original author when you use or modify this code.