Blackpine Cipher
A separate Blackpine application for file encryption. The corporate site describes the project boundary; release-specific cryptographic claims belong to the current application documentation and verified implementation.
A separate security surface
Cipher is hosted separately from the Blackpine corporate site so the application does not inherit marketing dependencies. Support and verification also operate on separate hostnames.
Engineering principles
- Security-sensitive behavior should be documented and testable.
- Threat-model language should describe assumptions and limits rather than rely on absolute security claims.
- Cryptographic claims should trace back to current implementation details, tests, or independent review.
- Marketing, verification, support, and application surfaces should remain distinct where their trust requirements differ.
Security model
The public project overview stays intentionally stable. The current threat model, test vectors, verification workflow, and release-specific cryptographic details belong with the project documentation so they can change with the implementation instead of drifting out of sync.
Application
Use the dedicated Cipher and Verify hostnames for the application and release verification surfaces.