Главная
Study mode:
on
1
Intro
2
Problem: Protecting Secrets against Timing Attacks
3
Solution: Constant-Time Programming (CT)
4
Constant-Time is Generally not Preserved by Compilers (1)
5
The Need for Automatic Analysis
6
Lots of Verification Tools for Constant-Time
7
Definition: Bug-Finding & Bounded-Verif for Constant-Time
8
Adapt SE for Constant-Time: Technical Key Insights
9
Contributions
10
Standard Approach eg (1.2 ): Symbolic Execution for Constant-Time via Self-Composition
11
Better Approach: Relational Symbolic Execution (1.2)
12
Dedicated Optimizations for Constant-Time Analysis
13
Binsec/Rel: Experimental Evaluation
14
Scalability: Comparison with RelSE (RQ2)
15
Effect of Compiler Optimizations on Constant-Time (RQ1/RQ3)
16
Conclusion
Description:
Explore a 16-minute IEEE conference talk on Binsec/Rel, an efficient relational symbolic execution tool for verifying constant-time programming at the binary level. Learn about the challenges of writing constant-time code to prevent timing side-channel attacks and the importance of binary-level analysis. Discover how Binsec/Rel improves upon previous symbolic execution techniques with optimizations for information flow and binary-level analysis. Examine the tool's effectiveness in bug-finding and bounded-verification through extensive experiments on cryptographic implementations. Gain insights into the impact of compiler optimizations on constant-time preservation and understand why binary-level reasoning is crucial for ensuring security in cryptographic code.

Efficient Relational Symbolic Execution for Constant-Time at Binary-Level

IEEE
Add to list
0:00 / 0:00