constant-time-testing

Detect timing side-channel vulnerabilities in cryptographic implementations using dudect and timecop.

Updated Feb 13, 2026
One-click install
npx skills add https://github.com/fjor1025/InfoSec-Framework --skill constant-time-testing-fjor1025
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: constant-time-testing
Source: https://github.com/fjor1025/InfoSec-Framework/tree/main/ClaudeSkills/plugins/testing-handbook-skills/skills/constant-time-testing
Command: npx skills add https://github.com/fjor1025/InfoSec-Framework --skill constant-time-testing-fjor1025

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps identify and mitigate timing side-channel vulnerabilities in cryptographic code, which can be exploited to leak sensitive information.

Core Features & Use Cases

  • Detect Timing Leaks: Utilizes statistical analysis (dudect) and dynamic tracing (timecop) to find execution time differences correlated with secret data.
  • Pinpoint Vulnerabilities: Identifies specific code locations responsible for timing leaks, such as conditional branches or secret-dependent memory accesses.
  • Use Case: When auditing a new cryptographic library, use this Skill to automatically run statistical tests and dynamic analysis to ensure no secret keys can be leaked through timing variations.

Quick Start

Use the constant-time-testing skill to analyze the provided C code for timing vulnerabilities.

Frequently Asked Questions about constant-time-testing

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I detect timing side-channel vulnerabilities in cryptographic code?

You detect timing side-channel vulnerabilities by applying statistical testing with dudect and dynamic tracing with timecop to cryptographic code. This identifies execution time differences correlated with secret data, specifically pinpointing secret-dependent branches, array accesses, and variable-time operations.

What is a timing attack and how does it leak cryptographic secrets?

A timing attack leaks cryptographic secrets by exploiting execution time variations in code handling sensitive material. When conditional branches or memory accesses depend on secret data, attackers statistically analyze these timing differences to extract sensitive information like cryptographic keys.

How do I audit a cryptographic library for secret-dependent branches and memory accesses?

You audit a cryptographic library for secret-dependent branches and memory accesses by running statistical tests and dynamic analysis. Employing dudect for statistical testing and timecop for dynamic tracing ensures no secret keys leak through timing variations in the cryptographic implementation.

Can I use dudect and timecop for vulnerability testing of crypto protocols?

Yes, you can use dudect and timecop for vulnerability testing of crypto protocols. This Skill applies dudect for statistical testing and timecop for dynamic tracing to audit crypto primitives and protocols, satisfying requirements for identifying variable-time operations and secret-dependent array accesses.

What's the best way to find variable-time operations in C code handling sensitive material?

The best way to find variable-time operations in C code handling sensitive material is combining statistical analysis with dynamic tracing. This Skill uses dudect to find execution time differences correlated with secret data and timecop to dynamically trace and pinpoint specific vulnerable code locations.