Skip to content

R11 — GET CHALLENGE and RNG health

Status: NOT EXECUTED as a complete hardware procedure — T2B1 and T3B1.

Use the shared acceptance record, with a separate result for every required model/OS. Host and emulator output remains separate evidence.

Preconditions

Recognised physical PC/SC reader; no debuglink; RNG status under Cryptography → Random; fault injection limited to a separate test image.

Steps

  1. Without an application PIN check, send opensc-tool -s 0084000001 and opensc-tool -s 0084000020; verify exactly 1 and 32 bytes before 9000.
  2. Try length 33 (opensc-tool -s 0084000021), absent length and a burst. Verify rejection/anti-abuse behavior against the AES/RNG profile.
  3. Record on-device RNG status/information, authenticate and run the self-test, then repeat GET CHALLENGE. Repeat after power loss and USB-mode changes.
  4. With the dedicated injection harness, simulate a stuck source/health failure and verify that no bytes are returned, including through key-generation calls. Document the injection and separate image hash. Recheck normal behavior on the actual candidate afterward.

Expected result

Correct lengths, hardware RNG path, health failures block output, rate/abuse limits apply. Histograms or differing outputs alone do not prove physical entropy.

Evidence to retain

APDU responses/lengths, screen/self-test status, injection method/errors and separate candidate/instrumented hashes.