KEVOS
ArticlesServicesCase studiesAboutContact
ArticlesServicesCase studiesAboutContact
← ArticlesFermat's Little Theorem and Euler's TheoremEngineering · Engineering MathematicsLesson 546/887← PrevNext →
GuidePublished 7 Aug 2026Updated 13 Aug 20268 min readBy Kevin Jogin
On this page

Ask about this page

KEVOS AIFermat's Little Theorem and Euler's Theorem

KEVOS knowledge first · trusted web sources when needed

Engineering  /  Mathematics  — Integer Foundations

Fermat's Little Theorem and Euler's Theorem

Fermat's little theorem, Euler's generalisation, and their role as the foundation of primality testing and public-key cryptography.

Page KV-MATH-0315Reading time 4 minReviewed 2026-08-07Author Kevin Jogin

Executive summary

Fermat's little theorem says that raising any unit to the power of the group order returns the identity. Stated that way it is a special case of Lagrange's theorem and requires no number theory at all.

Its importance is entirely computational: it provides a fast necessary condition for primality, and it is the identity that makes RSA decryption invert RSA encryption.

Learning objectives

  1. State Fermat's little theorem and Euler's generalisation.
  2. Derive both from Lagrange's theorem.
  3. Apply the result to compute inverses and to test compositeness.

01The theorems

Theorem

Fermat's little theorem

If p is prime and p ∤ a, then a^{p−1} ≡ 1 (mod p).

Equivalently, for every integer a, a^p ≡ a (mod p).

Theorem

Euler's theorem

If gcd(a, n) = 1, then a^{φ(n)} ≡ 1 (mod n).

Euler's theorem contains Fermat's as the case n = p, where φ(p) = p − 1. Both are instances of a single group-theoretic fact: in a finite group of order m, every element satisfies g^m = e, because the order of an element divides the order of the group.

Note
This is worth internalising because it explains why the theorem generalises so freely. Nothing about the integers is used — only that Z_n* is a finite group of order φ(n). The same statement holds in any finite group, and it is Lagrange's theorem that does the work.

02Computational consequences

  • Fast inverses

    For prime p, the inverse of a is a^{p−2} mod p, computable by repeated squaring without running extended Euclid.

  • Exponent reduction

    Exponents can be reduced modulo φ(n) before exponentiating, since a^{k} = a^{k mod φ(n)} when gcd(a,n) = 1.

  • Compositeness certificate

    If a^{n−1} ≢ 1 (mod n) for some a coprime to n, then n is definitely composite — no factorisation needed.

  • RSA correctness

    Choosing ed ≡ 1 (mod φ(n)) makes (a^e)^d = a^{1 + kφ(n)} = a, which is exactly why decryption inverts encryption.

The third of these is the Fermat primality test, and it is the starting point for all practical primality testing. Its weakness is that the converse fails.

03Where the converse fails

Caution
Satisfying a^{n−1} ≡ 1 (mod n) does not make n prime. Composite numbers passing this test for a given base are called Fermat pseudoprimes to that base, and there exist composites — the Carmichael numbers — that pass for every base coprime to n. The smallest is 561 = 3 · 11 · 17.

This gap is the entire reason the Miller–Rabin test exists. It strengthens the Fermat condition by additionally checking the square roots of 1 encountered during the exponentiation, and no composite survives that stronger test for more than a quarter of the possible bases.

Fermat versus Miller–Rabin
TestCondition checkedComposites that pass
Fermata^{n−1} ≡ 1Pseudoprimes; Carmichael numbers pass for all bases
Miller–RabinFermat plus non-trivial square roots of 1At most 1/4 of bases, for every composite

04Frequently asked questions

Why is a^p ≡ a (mod p) the better statement of Fermat's theorem?

Because it holds for every integer a with no coprimality hypothesis. When p divides a both sides are 0 mod p, so the exceptional case is absorbed rather than excluded.

Can Euler's theorem be improved?

Yes. The smallest exponent working for all units is the Carmichael function λ(n), which divides φ(n) and is often strictly smaller. For n = 8, φ(n) = 4 but λ(n) = 2, since every odd square is 1 mod 8.

Does the theorem give an efficient primality test on its own?

It gives an efficient compositeness test — a failure is conclusive. It gives no proof of primality, because Carmichael numbers pass for every base, so passing establishes nothing definite.

Related pages

  • The Fermat Test and Carmichael Numbers
  • Cyclic Groups
  • Euler's Phi Function
  • Arithmetic Functions and Mobius Inversion

Sources and method

Structural reference: Victor Shoup, A Computational Introduction to Number Theory and Algebra, Version 1, Cambridge University Press, 2005 — book pages 25-28.

This page carries the durable method layer only: definitions, constructions, algorithms, complexity results and selection criteria, authored originally for KEVOS. No text is transcribed or paraphrased from the source, and no numeric tables or benchmark data are reproduced — these are routed to live authoritative sources instead.

Author: Kevin Jogin. Last reviewed 2026-08-07.

Handbook application: from concept to controlled practice

Purpose. This expanded section turns the original page into a practical handbook. It preserves the supplied material and adds a repeatable way to apply, check and review Fermat's Little Theorem and Euler's Theorem. It does not replace a contract, legislation, a controlled standard, competent engineering judgement or specialist advice.

The operating aim is to turn a compact mathematical statement into a usable chain of definitions, claims, examples and checks. Read the original explanation first, then use the workflow and checks below to convert knowledge into evidence.

Treat Fermat's Little Theorem and Euler's Theorem as a network of definitions and implications, not as a list of formulas. The working vocabulary on this page—theorem, fermat's, little, euler's, generalisation—should be made explicit before any proof or computation begins. Record the ambient set or structure, the permitted operations and the equality or equivalence relation in use. A compact theorem often changes meaning when the base field, finiteness condition, commutativity assumption or direction of an action changes.

For a proof, write the hypotheses as a checklist and mark the line at which each one is used. For a computation, state the representation of the input, the arithmetic model, the termination condition and the output invariant. For a classification problem, distinguish existence from uniqueness and distinguish an object from its representation. These separations prevent a correct local calculation from being mistaken for the general result.

A useful worked example should be small enough to inspect completely but rich enough to exercise the main mechanism. Compute the result in two ways where practical: symbolically and by substitution, structurally and numerically, or directly and through a normal form. Then include one near-miss example in which a hypothesis fails. The contrast explains why the theorem is shaped as it is and gives the reader a diagnostic pattern for later problems.

Verification is part of the mathematics. Check domains and codomains, substitute proposed solutions, test identity and zero cases, compare dimensions or cardinalities, and confirm that maps respect the required operations. In numerical work, report precision, conditioning and a residual rather than digits alone. In algorithmic work, separate mathematical correctness from implementation complexity and resource limits.

Step-by-step operating method

  1. Fix the setting. State the objects, ambient structure, notation and assumptions before manipulating symbols.
  2. Separate claims. Distinguish definitions, hypotheses, conclusions, equivalent conditions and consequences.
  3. Choose a method. Select proof, construction, calculation or algorithm according to the question actually asked.
  4. Work a small case. Use the smallest non-trivial example to expose the mechanism and test edge behaviour.
  5. Verify independently. Substitute back, check invariants, test boundary cases or use an alternative derivation.

Worked-example protocol

Illustrative method—not a source theorem. Start with a small admissible input and list the definitions it must satisfy. Carry out each transformation on a separate line, citing the property that permits it. Preserve exact values until approximation is necessary. At the end, verify the output against the original definition and one invariant such as dimension, degree, determinant, order, norm or residual. Then alter one hypothesis and observe which step ceases to be valid. This protocol creates a reusable example without inventing a theorem-specific numerical answer.

StageRecordQuality check
InputObjects, domain, notation, assumptionsEvery symbol is defined
MethodPermitted operation or cited result at each stepAll hypotheses hold
OutputExact result and representationCorrect type, domain and form
VerificationSubstitution, invariant or alternative derivationIndependent agreement
Boundary testZero, identity, degenerate or failed hypothesisScope is understood

Common failure modes and recovery actions

1. Watch for

Using a theorem without checking every hypothesis.

Recovery: Return to the governing definition or requirement and restate the decision in one sentence.

2. Watch for

Treating a suggestive example as a proof of the general case.

Recovery: Separate evidence from assumption, assign an owner and set a date for validation.

3. Watch for

Changing notation or conventions part-way through an argument.

Recovery: Run a small counterexample, boundary test, pilot or independent check before proceeding.

4. Watch for

Hiding a division-by-zero, convergence, finiteness or commutativity assumption.

Recovery: Record the consequence, decision and rationale, then update the controlled baseline.

5. Watch for

Reporting a computed result without a residual, substitution or structural check.

Recovery: Escalate when the issue affects safety, compliance, acceptance, material value or an agreed tolerance.

Review checklist

  • Can every symbol be traced to a definition or prior result?
  • Which hypothesis does each major step use?
  • Does the method cover zero, identity, degenerate and boundary cases?
  • Can the conclusion be checked by a second representation or calculation?
  • Are mandatory requirements distinguished from recommendations and illustrative values?
  • Are sources, assumptions, units, dates and versions recorded closely enough to reproduce the decision?
  • Have safety, legal, ethical, stakeholder and operational consequences been considered at the appropriate level?
  • Is there a named owner and a trigger for review, escalation, change or retirement?

Questions for deeper application

What is the most important distinction a practitioner must preserve when applying Fermat's Little Theorem and Euler's Theorem?

Answer with a fact or cited source where available. Where evidence is incomplete, record the assumption, consequence, responsible owner and next validation action.

Which assumption about theorem would change the result most if it proved false?

Answer with a fact or cited source where available. Where evidence is incomplete, record the assumption, consequence, responsible owner and next validation action.

What evidence would allow an independent reviewer to reproduce or challenge the conclusion?

Answer with a fact or cited source where available. Where evidence is incomplete, record the assumption, consequence, responsible owner and next validation action.

Which boundary, exception or failure case has not yet been tested?

Answer with a fact or cited source where available. Where evidence is incomplete, record the assumption, consequence, responsible owner and next validation action.

What must be handed over, monitored or reviewed after the immediate work is complete?

Answer with a fact or cited source where available. Where evidence is incomplete, record the assumption, consequence, responsible owner and next validation action.

Authoritative references and use notes

The sources below were selected as institutional or primary guidance for the broader practice. They support the handbook method; they do not imply that every statement or clause in a source applies to every project. Confirm the current edition, jurisdiction, contract and application before treating any requirement as mandatory.

  • MIT OpenCourseWare — Algebra I — Massachusetts Institute of Technology. Used for groups, vector spaces, linear transformations and linear groups. Accessed 2026-08-13.
  • The Stacks Project — table of contents — The Stacks Project. Used for commutative algebra, homological algebra, modules and derived categories. Accessed 2026-08-13.

Continue learning

Euler's Phi FunctionGuide · Engineering MathematicsNEXT LESSON →Arithmetic Functions and Mobius InversionGuide · Engineering MathematicsThe Chinese Remainder TheoremGuide · Engineering MathematicsAsymptotic Notation for Algorithm AnalysisGuide · Engineering Mathematics
KEVOS · Engineering, manufacturing and project improvement
ArticlesServicesCase studiesAboutContact
© 2026 KEVOS®