constant-time-testing

Detect timing vulnerabilities in cryptographic implementations using dudect and timecop.

Updated Apr 5, 2026
One-click install
npx skills add https://github.com/balic-AI-ML-R-D-Resources/eliza_autonomous_agents --skill constant-time-testing-balic-ai-ml-r-d-resources
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: constant-time-testing
Source: https://github.com/balic-AI-ML-R-D-Resources/eliza_autonomous_agents/tree/main/packages/skills/skills/testing-handbook-skills/skills/constant-time-testing
Command: npx skills add https://github.com/balic-AI-ML-R-D-Resources/eliza_autonomous_agents --skill constant-time-testing-balic-ai-ml-r-d-resources

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Timing vulnerabilities in cryptographic code cause secret-dependent execution times that can leak keys. This Skill provides a structured approach to detect, analyze, and remediate constant-time violations using a combination of statistical tests, dynamic tracing, and formal verification.

Core Features & Use Cases

  • Statistically detect leaks with dudect across input classes.
  • Pinpoint leak sources with Timecop dynamic tracing.
  • Provide remediation guidance and CI-ready checks for crypto libraries. Use cases include auditing OpenSSL-like crypto code, RSA/ECDSA implementations, and post-quantum crypto.

Quick Start

Run a dudect-based analysis on your crypto function to determine if timing leaks exist.

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 leaks in cryptographic code?

Constant-time testing uses statistical analysis and dynamic tracing to verify that cryptographic implementations execute in uniform time regardless of secret inputs, preventing timing side-channel attacks.

What is the best way to audit crypto primitives for constant-time behavior?

Auditing crypto primitives for constant-time behavior involves applying structured testing workflows that combine dudect statistical leak detection with timecop dynamic tracing to pinpoint violations across architectures.

How do I pinpoint the source of a timing vulnerability in RSA or ECDSA implementations?

You can pinpoint the source of a timing vulnerability in RSA or ECDSA implementations by using timecop dynamic tracing to trace execution paths and identify exact secret-dependent operations causing the leak.

Can I integrate constant-time testing into my CI pipeline for crypto libraries?

Yes, you can integrate constant-time testing into your CI pipeline by configuring dudect and timecop checks to automatically audit crypto libraries and enforce constant-time behavior on every commit.

Does constant-time testing work for post-quantum cryptographic implementations?

Constant-time testing applies to post-quantum cryptographic implementations by running statistical tests and dynamic tracing to ensure constant-time behavior across secret inputs and different hardware architectures.

Why does my cryptographic implementation fail constant-time checks across different architectures?

Cryptographic implementations fail constant-time checks across architectures when secret-dependent execution times leak keys, requiring statistical tests and dynamic tracing to detect and remediate the specific timing violations.