Security status and reporting
Security
Clear boundaries for historical cryptographic material, future supported code, and responsible vulnerability reporting.
No historical package on this site should be assumed secure or suitable for a current production system.
1. Historical software
- •Historical releases may depend on obsolete libraries and protocols.
- •Archived instructions may describe unsupported operating systems and compiler versions.
- •Historical cryptographic guidance is preserved for research, not presented as a current recommendation.
2. Future security policy
- •Publish supported versions and response expectations.
- •Provide a private vulnerability-reporting channel.
- •Coordinate disclosure and remediation before public discussion.
- •Document cryptographic design claims and their review status.
3. Current reporting
Security concerns involving the website or preserved files can be submitted through the contact page. A dedicated security address will be published before supported software is released.
Interested in helping before the public repository opens? Contact TwoSquares with your area of interest or any historical material you can verify.