liveBook · Manning

Cryptographic implementation

A cryptographic implementation is a software or hardware realization of cryptographic algorithms, constructions, or protocols.

How 2 Manning books explain it

Real-World Cryptography

A cryptographic implementation is executable software that realizes a cryptographic algorithm, construction, or protocol.

How it is used
Guides developers toward safe, interoperable cryptographic software and away from unnecessary custom implementations.
How deep it goes
Explains implementation choice, standards, interfaces, and testing, but stops short of implementation-level code or formal verification details.
Examples
Uses AES, ECDSA, AES-GCM, Google’s Tink, libsodium, cryptography.io, and Wycheproof test vectors as concrete examples.
What you can do after
Diagnose implementation risk, select established libraries, read usage constraints, and test cryptographic code with relevant vectors.

Read how Real-World Cryptography explains cryptographic implementation →

Hacking Cryptography

A software or hardware realization of cryptographic theory that performs cryptographic operations in a system.

How it is used
Deploys cryptographic algorithms as security mechanisms while emphasizing engineering failures and safer implementation choices.
How deep it goes
Connects implementation failures to randomness, side channels, control flow, memory, types, and atomicity, but does not develop each mechanism fully.
Examples
Uses the PlayStation 3 private-key failure, OpenSSL, TLS, and rainbow-table implementation as concrete engineering examples.
What you can do after
Apply cryptography via established implementations and diagnose common implementation weaknesses before deployment.

Read how Hacking Cryptography explains cryptographic implementation →

Related concepts

These guides are generated from the text of Manning books by Manning's knowledge graph and link to the sections they draw on. The full books are available on liveBook and at manning.com.