Hash vs Encryption vs Signature: Three Different Jobs

Hashes verify data hasn't changed. Encryption keeps data secret. Digital signatures prove WHO sent it — and that they can't deny it.

Hash vs Encryption vs Signature: Three Different Jobs

Developers often confuse these three cryptographic primitives. Here's the clear distinction:

The critical difference: anyone can compute a hash, but only the private key holder can create a valid signature.

import hashlib, hmac, secrets

message = b"Transfer $500 to Alice"

# HASH — anyone can compute it
digest = hashlib.sha256(message).digest()
print(f"Hash: {digest.hex()[:32]}...")

# ENCRYPTION — hides the content
key = secrets.token_bytes(32)
ciphertext = bytes(a ^ b for a, b in zip(message, key * len(message)))
print(f"Encrypted: {ciphertext.hex()[:32]}...")

# SIGNATURE — proves WHO sent it
private_key = secrets.token_bytes(32)
signature = hmac.new(private_key, message, hashlib.sha256).digest()
print(f"Signature: {signature.hex()[:32]}...")

The Three Properties of Digital Signatures

Without all three, you don't have a proper digital signature. A hash provides integrity but not authentication. Encryption provides confidentiality but not non-repudiation. Only signatures provide all three.

How Signing Works: Step by Step

The signing process has two phases: sign (sender) and verify (receiver).

# Step 1: Sender creates document
document = b"Purchase Order #12345: 100 widgets at $10 each"

# Step 2: Sender signs with PRIVATE key
private_key = secrets.token_bytes(32)
signature = hmac.new(private_key, document, hashlib.sha256).digest()
# signature = Sign(document, private_key)

# Step 3: Send document + signature
# (anyone can intercept — they can't forge without private key)

# Step 4: Receiver verifies with PUBLIC key
recomputed = hmac.new(private_key, document, hashlib.sha256).digest()
valid = recomputed == signature
print(f"Signature valid: {valid}")  # True

The key insight: verification uses the same private key as signing (in this simplified demo). In real systems, the public key can verify without knowing the private key.

Tamper Detection in Action

One of the most powerful properties of signatures is tamper detection. Even a single character change invalidates the signature:

Hash Algorithms for Signatures

Digital signatures don't sign the raw data — they sign a hash of the data. The choice of hash algorithm matters:

Most modern signatures use SHA-256 or better. MD5 and SHA-1 have known collision attacks and should never be used for signatures.

Signature Algorithms Compared

The NIST post-quantum standards (ML-DSA and SLH-DSA) finalize in 2024. For new systems, consider quantum-resistant algorithms.

Where You Already Use Digital Signatures

You encounter digital signatures daily, even if you don't realize it:

Sign-Then-Encrypt vs Encrypt-Then-Sign

When you need both confidentiality AND authentication, the order matters:

Most protocols (TLS, S/MIME, PGP) use sign-then-encrypt or its equivalent.

Try It Yourself

Start with the hash comparison tool to understand different algorithms, then explore the HMAC generator to see how keys create signatures.

Further Reading

• Zero-Knowledge Proofs Explained — Advanced proof techniques
• Post-Quantum Cryptography Explained — Future-proof signatures
• How HTTPS and TLS Actually Work — Where certificates are signed
• Why Developers Should Care About PQC — Quantum threats to signatures
• OAuth 2.0 Explained — Authentication protocol comparison

All cryptographic examples use HMAC for educational simplicity. Production systems use RSA-PSS, ECDSA, or EdDSA from peer-reviewed libraries.