🔍 Evidence Hashing
WebCrypto SHA-256 / SHA-384 / SHA-512
Cryptographic Evidence Hashing: Browser's WebCrypto API computes mathematically secure hash fingerprints — the same standard used by law enforcement agencies and government forensic laboratories worldwide.
Hash yahan aayega...
Compute karo pehle...
—
🔄 Tamper Detection — Hash Integrity Comparison
SHA-256 Verified
Compare two evidence strings using cryptographic hashing. Even a single character modification produces a completely different hash — demonstrating evidence integrity verification.
✍️ ECDSA Digital Signature Authentication
WebCrypto ECDSA P-256
Industry-Standard Digital Signatures: ECDSA P-256 keys are generated using the browser's WebCrypto API — the same algorithm currently used in courts for evidence authentication. In a post-quantum system, this will be replaced by CRYSTALS-Dilithium3 (FIPS 204).
1
Key Generate Karo2
Evidence Sign Karo3
Verify Karo4
Tamper DetectStep 1 — Key Pair Generation
Key generate karo pehle...
Key generate karo pehle...
Step 2 — Evidence Signing
Pehle keys generate karo...
Step 3 — Verify & Tamper Detection
🔒 AES-256-GCM Evidence Encryption
WebCrypto AES-256-GCM
Military-Grade Encryption Standard: AES-256-GCM is the encryption standard approved for classified government documents by NSA and adopted by law enforcement agencies globally. GCM mode provides both confidentiality and authenticity verification.
🔒 Encrypt Evidence
Encrypt karo pehle...
—
🔓 Decrypt Evidence
Decrypt karo pehle...
PQC Integration: In a production post-quantum system, the AES-256 encryption key is protected using CRYSTALS-Kyber-768 KEM (FIPS 203) instead of a password. This hybrid approach — AES-256 for data confidentiality, Kyber-768 for quantum-resistant key encapsulation — is the recommended NIST migration strategy.
🔗 Digital Evidence Chain of Custody
SHA-256 Hash Chain Verification
Cryptographic Chain of Custody: Each custody transfer generates a real SHA-256 hash. Any tampering at any stage breaks the chain — providing mathematically provable evidence integrity for court admissibility.
Build karo pehle...
⚛️ Post-Quantum Cryptography Algorithm Suite
NIST FIPS 203-206 — Browser Native Support Pending
Why Simulated? CRYSTALS-Dilithium, Kyber-768, and FALCON are not yet natively supported in browser WebCrypto APIs (expected 2025-2026). For production PQC, Python/liboqs or OpenSSL 3.x with OQS provider is required. This module demonstrates accurate key sizes, signature structures, and workflows as defined in NIST FIPS 203-206.
—
—
Select algo and generate...
📊 Classical vs Post-Quantum Algorithm Comparison
| Algorithm | Public Key | Signature | Quantum Safe | Status |
|---|---|---|---|---|
| ECDSA P-256 | 64 bytes | 72 bytes | ❌ NO | DEPRECATED |
| Dilithium3 | 1,952 bytes | 3,293 bytes | ✅ YES | FIPS 204 |
| FALCON-512 | 897 bytes | ~666 bytes | ✅ YES | FIPS 206 |
| SPHINCS+-256s | 64 bytes | 49,856 bytes | ✅ YES | FIPS 205 |
| Kyber-768 | 1,184 bytes | 1,088 bytes (CT) | ✅ YES | FIPS 203 |
🖥️ Operation Log
// Post-Quantum Cryptography — Digital Evidence Integrity System
// SHA-256 | ECDSA P-256 | AES-256-GCM — WebCrypto API (Production Grade)
// Dilithium3 | Kyber-768 | FALCON — NIST FIPS 203-206 (Simulated)
pqc-evidence-system:~$ _