liveBook · Manning

AES

As explained in Hacking Cryptography

A symmetric block-cipher standard adopted for protecting data in applications ranging from financial transactions to classified information.

AES is a symmetric block-cipher standard for protecting data, including financial transactions and classified information. Also called Rijndael, it replaced DES after a public selection process and remains secure against known practical attacks when implemented correctly. section 1.3 section 5.1

AES defines a family of configurations with these core properties:

When correct AES still fails

An attacker need not break AES’s mathematical theory. A padding-related implementation bug can expose plaintext encrypted by an AES-based system, making the engineering around the cipher the practical attack surface. section 1.3 section 5.1

The operational rule is simple: distinguish the cipher from the system using it. Correctly implemented AES has no known practical attacks, while bugs and unanticipated interactions with machines and data can repeatedly compromise AES-based systems. section 1.3

How Hacking Cryptography covers it

How deep it goes
Defines AES’s structure, key sizes, and security status, then stops short of detailing its round transformations or algorithms.
Examples
Uses bank transactions, classified data, and padding bugs that expose AES-encrypted plaintext as concrete examples.
What you can do after
Diagnose AES deployments by separating attacks on the cipher’s theory from failures in padding and other implementation details.
How it connects
Relates AES to Rijndael, DES, 3DES, block ciphers, padding, and implementation vulnerabilities.

Also explained in

Compare how 2 books explain AES →

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Hacking Cryptography. The section links point to the parts of the book it draws on.