aol.pm

Cryptographic timing attack

Historical concept · local-technique:cryptographic-timing

Attributed source ↗ · Plaintext record · Complete record and assertions JSON

Timing observations may reveal secret-dependent implementation behavior.

Constant-time implementations, appropriate blinding and measured leakage testing.

A cryptographic timing milestone, not the origin of every timing or covert-channel concept.

Documented publication credit

Timing Attacks on Implementations of Diffie-Hellman, RSA, DSS, and Other Systems — Paul C. Kocher (research author). This is a publication record, not an origin or invention claim.

Inspect structured metadata and provenance
{
  "id": "local-technique:cryptographic-timing",
  "title": "Cryptographic timing attack",
  "type": "Historical concept",
  "snapshot": "historical-seed.json",
  "source_url": "https://paulkocher.com/doc/TimingAttacks.pdf",
  "description": "Timing observations may reveal secret-dependent implementation behavior.",
  "defensive_context": "Constant-time implementations, appropriate blinding and measured leakage testing.",
  "publication": {
    "id": "local-publication:cryptographic-timing-milestone",
    "entity_type": "Publication",
    "title": "Timing Attacks on Implementations of Diffie-Hellman, RSA, DSS, and Other Systems",
    "source_url": "https://paulkocher.com/doc/TimingAttacks.pdf",
    "publication_date": "1996",
    "publisher": "CRYPTO96",
    "credit_display": "Paul C. Kocher",
    "credit_role": "research author"
  },
  "mappings": [
    {
      "target_id": "CWE-208",
      "relation": "underlying observable timing weakness",
      "status": "research-supplied conceptual mapping; target exists in imported taxonomy; semantic review pending"
    }
  ],
  "uncertainty": "A cryptographic timing milestone, not the origin of every timing or covert-channel concept.",
  "rights": "Original concise metadata and linked references; no full paper or payload imported",
  "review_status": "Editorial historical seed; conceptual mappings remain explicitly provisional"
}

Explicit source assertions (0)

First 80 shown here; the complete set is in this record’s JSON and plaintext. Each relationship retains its source and locator. No inferred relationships are added.

Provided as is, for information only, with no warranty and no liability. Not legal or professional advice. Security and radio material is for authorized, lawful use only. Full disclaimer.

Visits are logged on our own server: IP address, browser and device details, and pages viewed. We use them to understand traffic and spot attacks, and never share or sell them.