hesela.devAuthenticated encryption
Authenticated encryption combines confidentiality with cryptographic integrity protection for the protected message.
AEAD additionally authenticates associated data without encrypting it; another layer may protect its confidentiality. RFC 5116 defines decryption as returning plaintext or failure and requires compliance with the chosen algorithm's nonce rules. It leaves anti-replay services and access decisions outside the interface. [1] A storage design therefore needs a separate trusted freshness mechanism if it must reject older valid data. [2]
Relations
- related
- xts-aes, cryptographic-nonce, dm-crypt, luks, dm-integrity, cryptographic-hash, lost-write, replay-attack, rollback-protection
Limitations
- Authentication does not repair damaged bytes or prove that a write was durable; those are separate storage contracts. [3]