Crypt-ro - Blazing Fast Matrix-Based Cryptographic Library
A high-performance Rust library implementing lightning-fast matrix-based cryptographic operations that outperform traditional algorithms like RSA in most use cases.
Why Choose Crypt-ro?
ð 10-100x faster than RSA for typical payloads
ð Secure by design with multiple protection layers
⥠Near-native performance thanks to Rust optimization
âĻ Text-friendly URL-safe base64 encoding
ð§Đ Support for both raw bytes and text operations
ð Perfect for high-throughput applications like:
- Real-time messaging
- Database encryption
- Game networking
- IoT device communication
Features
- Lightning-fast operations optimized
- Constant-time operations resistent to timing attacks
- Minimal overhead with efficient memory usage
- Thread-safe design for parallel processing
Installation
Add to your Cargo.toml:
[]
= "1.0.0"
Usage Example
use Cryptor;
Basic Text Encryption
use Cryptor;
Binary Data Encryption
use Cryptor;
Custom Matrix Size
use Cryptor;
When to Use
â
High-volume encryption (logging, metrics, telemetry)
â
Low-latency requirements (real-time systems)
â
Resource-constrained environments
â
Temporary data protection (session tokens, cache)
Performance
Crypt-ro delivers blazing-fast encryption/decryption speeds, competitive with industry-standard algorithms:
| Algorithm | Operation | 50B Data | Comparison |
|---|---|---|---|
| Cryptor | Encrypt | 343-350 ns | Reference |
| Cryptor | Decrypt | 369-370 ns | Reference |
| AES-256-GCM | Encrypt | 460-461 ns | ~1.3x slower |
| AES-256-GCM | Decrypt | 459-460 ns | ~1.3x slower |
| RSA-2048 | Encrypt | 172.26-172.29 Ξs | ~500x slower |
| RSA-2048 | Decrypt | 1.424-1.426 ms | ~4000x slower |
Key Advantages:
- ⥠Sub-microsecond operations for small data
- ðĨ Decryption is 15-20% faster than AES-256-GCM
- ð 3000x faster than RSA for decryption
Security Considerations
While extremely fast, Crypt-ro uses:
- Random initialization vectors
- Multiple transformation layers
- Defense in depth strategy Security Notes
- This library uses a custom encryption algorithm - not peer-reviewed
- Not recommended for highly sensitive data
- Always use strong, complex keys
Contributing
Contributions are welcome! Please open an issue or pull request on GitHub.
License
Dual-licensed under MIT or Apache 2.0 at your option.