This roadmap outlines the planned development phases for the quantum-tunneler project.
- Set up workspace with modular crates
- Define core modules: crypto, ike, ipsec, utils
- Create initial CLI with basic
initcommand - Write base documentation (README, architecture, phases)
- Prepare
no_stdcompatibility via feature flags
- Implement Kyber512 (Key Encapsulation Mechanism)
- Implement Falcon512 (Digital Signature Scheme)
- Implement Dilithium3 (Digital Signature Scheme)
- Implement SPHINCS+ (Digital Signature Scheme)
- Provide generic crypto interfaces (traits)
- Add unit tests with official test vectors
- Implement IKEv2 Phase 1 (Main Mode)
- SA_INIT exchange
- AUTH exchange with post-quantum signatures
- Implement IKEv2 Phase 2 (Quick Mode)
- CHILD_SA negotiation
- Key derivation using Kyber
- Implement Security Association management
- SA database
- SA lifetime management
- Rekeying procedures
- Implement ESP header processing
- Implement tunnel mode encapsulation
- Add replay protection
- Implement packet authentication
- Add SA and security policy management
- Implement packet fragmentation handling
- Add CLI commands:
-
connect- Establish VPN tunnel -
status- Show tunnel status -
simulate- Run attack simulations -
benchmark- Performance testing
-
- Support multiple sessions
- Add real-time tunnel monitoring
- Implement JSON output format
- Add structured logging
- Performance evaluation:
- Handshake speed
- Tunnel throughput
- CPU/memory usage
- Security testing:
- MITM attack simulation
- Replay attack testing
- Forward secrecy verification
- Comparison with classical IPSec:
- RSA/ECDH performance
- Security guarantees
- Resource usage
- Publish core crate to
crates.io - Generate API documentation via
docs.rs - Release open-source version on GitHub
- Publish technical articles
- Create example applications
- QUIC protocol integration
- MicroVM (Firecracker) secure tunnel hosting
- Web dashboard UI
- WireGuard-style performance profile
- Hardware acceleration support
- Cloud deployment templates
💡 The project is actively developed. Community feedback and contributions are encouraged. Visit our GitHub repository to get involved.