liveBook · Manning

Brute-force search

As explained in Hacking Cryptography

A brute-force search systematically tests possible candidates until one satisfies the required conditions.

Brute-force search tests candidate values systematically until one satisfies the required conditions. Recovering an unknown LFSR length becomes practical when each candidate is checked by matrix inversion. section 4.2.2

How Hacking Cryptography covers it

How deep it goes
Demonstrates candidate enumeration, matrix inversion, decryption, and validation, stopping short of deriving the more efficient Berlekamp–Massey algorithm.
Examples
Demonstrates recovery from an ATTACK AT prefix and validates the decrypted timestamp against a concrete test message.
What it assumes
Assumes known plaintext, ciphertext, XOR, observed keystream bits, and matrix inversion while teaching the recovery workflow concretely.
What you can do after
Diagnose and exploit recoverable LFSR ciphertext by testing lengths, reconstructing taps, and validating decrypted plaintext.
How it connects
Connects LFSRs with known-plaintext attacks, XOR, matrix inversion, and Berlekamp–Massey algorithm.

Also explained in

Compare how 7 books explain brute-force search →

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.