File vault
AES-256-GCM · Passwords or key files
SECURITY WORKSPACE
Sign in to encrypt, analyse and transfer files between accounts.
CIPHERVAULT / ACCOUNT WORKSPACE
Your encrypted private signing key belongs to this account. Keep its passphrase separate from file passwords.
YOUR SECURITY WORKSPACE
Protect your files. Verify their origin. Explore the science behind every bit.
AES-256-GCM · Passwords or key files
Send encrypted files to another account.
SHA-256 · RSA-PSS
Confidentiality: AES-256-GCM encrypts file contents. Integrity: GCM rejects modified packages; SHA-256 compares recovered bytes. Authenticity: RSA-PSS verifies signed content relative to a public key you trust.
Account transfers pass ciphertext through private hosted storage. File passwords, keys and recovered plaintext stay in your browser. Numeric measurements are saved per account.
Use two accounts in a normal tab and incognito, or on separate devices. Share the file password and trusted signing fingerprint separately.
Transfer expires after 24 hours. Sender may delete it earlier.
Verified sender signature over the transfer manifest and file hashes.
Text security metrics: confusion, diffusion and avalanche effect. Compare measured bit-level and character-level changes with the ideals of 50% and 100%. This controlled experiment is separate from the transferred file.
Share this fingerprint with the receiver through a trusted channel.
Sender and receiver signatures bind the manifest and recovery claim. Device clocks are not trusted timestamp-authority evidence.
Export a bundle from any transfer above. Verification runs in this browser with no server request; compare both signing fingerprints through a trusted channel.
Matching hashes do not independently authenticate a sender.
Signatures establish authenticity only relative to a trusted public key.
Preimage: find an input for a given hash. Second preimage: find a different input with the same hash as a fixed input. Collision: find any two different inputs with the same hash.
Generates 20 values and their SHA-256 hashes, then runs bounded preimage, second-preimage and collision searches. Each full-digest search is capped at 5,000 candidates. The graph also shows theoretical work near 2^256 for fixed targets and 2^128 for collisions; these enormous counts are estimates, not executed searches.
Actual Python server measurements · six sizes · three trials per size.
EXPERIMENT / OBSERVE / VERIFY
Change a single bit. Follow its impact. Put integrity to the test.
Encrypt your text, recover it, then flip one ciphertext bit. Watch AES-GCM enforce integrity in your browser.
Ready for your first challenge.
Fresh ephemeral AES-256 key and nonce per run. This experiment does not save your text or keys. GCM authenticates the ciphertext; sender identity requires a trusted signature.
Twenty generated values are hashed and compared. Full SHA-256 searches have a 5,000-attempt budget per trial; theoretical 2^256 and 2^128 work is shown separately from measured results.
Explore a Wireshark packet capture from your file-transfer demo. Import a packet-summary CSV to generate charts and inspect the traffic.
Upload a Wireshark packet-summary CSV to explore charts and packets.
CSV export · up to 10 MiB / 100,000 packets
What the imported packet summaries reveal to an observer. Estimates describe frame traffic, not the encrypted file contents.
Top 20 by sent + received frame bytes.