KEVOS
ArticlesServicesCase studiesAboutContact
ArticlesServicesCase studiesAboutContact
← ArticlesGenerating a Random Prime Between 2 and MEngineering · Engineering MathematicsLesson 619/887← PrevNext →
GuidePublished 7 Aug 2026Updated 13 Aug 20268 min readBy Kevin Jogin
On this page

Ask about this page

KEVOS AIGenerating a Random Prime Between 2 and M

KEVOS knowledge first · trusted web sources when needed

Engineering  /  Mathematics  — Primality Testing

Generating a Random Prime Between 2 and M

Generating a uniform random prime below a bound, the analysis of the retry loop, and the resulting output distribution.

Page KV-MATH-0389Reading time 3 minReviewed 2026-08-07Author Kevin Jogin

Executive summary

Drawing uniform candidates below a bound and testing each until one is prime yields a prime distributed uniformly over the primes in range.

The expected number of candidates follows from the prime number theorem, and the analysis is the geometric distribution applied to a known success probability.

Learning objectives

  1. State the generation procedure and its expected cost.
  2. Prove the output distribution is uniform.
  3. Handle the interaction between test error and output correctness.

01The procedure

Algorithm

Random prime below M

Inputbound M, round count k
Outputa prime in [2, M], uniform over primes in range
  1. Repeat:
  2.   Draw a uniform integer n from {2, ..., M}.
  3.   Apply trial division by small primes; if composite, continue.
  4.   Apply Miller-Rabin with k rounds; if composite, continue.
  5.   Return n.
  6. Until an iteration cap is reached.
Cost  expected ≈ ln M candidates

The success probability per candidate is π(M)/M ≈ 1/ln M, so the expected number of candidates is about ln M by the geometric distribution.

02Uniformity of the output

Theorem

Output distribution

If candidates are drawn uniformly and independently, and the test is applied identically to each, the returned value is uniform over the primes in the range.

Reason. Conditioned on acceptance, every prime was equally likely to have been the drawn candidate, and acceptance depends only on primality.

Caution
Both hypotheses are load-bearing. Drawing candidates by stepping from a previous failure destroys independence and biases the output towards primes following long gaps. Applying different numbers of rounds to different candidates would make acceptance depend on more than primality.

Uniformity matters where a security argument assumes it. For RSA the requirement is weak, but for schemes whose proofs quantify over uniformly chosen primes, a biased generator invalidates the reduction.

03Test error and output correctness

The output is prime only up to the error probability of the primality test. Two error sources compound and are worth separating.

Failure sources
SourceProbabilityConsequence
Miller-Rabin false positive≤ 4^{−k} per accepted candidateA composite is returned as prime
Cap exhausted≤ e^{−c}Failure reported; caller retries
Entropy failureNot quantifiableCorrelated or repeated outputs; catastrophic

Only the first affects correctness of a returned value. The second is a clean failure the caller can handle, and the third is outside the probabilistic model entirely — which is why entropy quality must be established by other means rather than folded into the analysis.

Note
Because the test is applied only to candidates surviving trial division, and because a random composite almost never passes even one Miller-Rabin round, the effective false-positive rate for randomly generated candidates is far below the worst-case 4^{−k}.

04Frequently asked questions

Does the trial division filter affect uniformity?

No, because it rejects only composites. Any filter whose acceptance depends solely on primality preserves uniformity over the primes; a filter that rejected some primes would not.

Why draw from {2,...,M} rather than a bit-length range?

This form is the clean case for analysis. Practical generation fixes a bit length instead, which restricts the range to [2^{k−1}, 2^k) and changes the density slightly without altering the argument.

How large should the iteration cap be?

A small multiple of ln M — a hundred times the expected count makes spurious failure negligible while still catching a broken entropy source promptly.

Related pages

  • Generating a Random Prime
  • The Miller-Rabin Primality Test
  • Trial Division up to a Small Bound

Sources and method

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

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 Generating a Random Prime Between 2 and M. 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 Generating a Random Prime Between 2 and M as a network of definitions and implications, not as a list of formulas. The working vocabulary on this page—random, prime, output, generating, below—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 Generating a Random Prime Between 2 and M?

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 random 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 — Number Theory I — Massachusetts Institute of Technology. Used for algebraic and analytic number theory. Accessed 2026-08-13.
  • MIT OpenCourseWare — Algebra I — Massachusetts Institute of Technology. Used for groups, vector spaces, linear transformations and linear groups. Accessed 2026-08-13.

Continue learning

The Miller-Rabin Primality TestGuide · Engineering MathematicsNEXT LESSON →Trial Division up to a Small BoundGuide · Engineering MathematicsThe Fermat Test and Carmichael NumbersGuide · Engineering MathematicsGenerating a Random k-Bit Prime with Miller-RabinGuide · Engineering Mathematics
KEVOS · Engineering, manufacturing and project improvement
ArticlesServicesCase studiesAboutContact
© 2026 KEVOS®