BEGIN:VCALENDAR
VERSION:2.0
PRODID:-//pretalx//cfp.pass-the-salt.org//pts2025//talk//RDEFF3
BEGIN:VTIMEZONE
TZID:CET
BEGIN:STANDARD
DTSTART:20001029T040000
RRULE:FREQ=YEARLY;BYDAY=-1SU;BYMONTH=10
TZNAME:CET
TZOFFSETFROM:+0200
TZOFFSETTO:+0100
END:STANDARD
BEGIN:DAYLIGHT
DTSTART:20000326T030000
RRULE:FREQ=YEARLY;BYDAY=-1SU;BYMONTH=3
TZNAME:CEST
TZOFFSETFROM:+0100
TZOFFSETTO:+0200
END:DAYLIGHT
END:VTIMEZONE
BEGIN:VEVENT
UID:pretalx-pts2025-RDEFF3@cfp.pass-the-salt.org
DTSTART;TZID=CET:20250703T142000
DTEND;TZID=CET:20250703T144000
DESCRIPTION:You meticulously craft constant-time code to protect against si
 de-channel attacks—only to have your compiler silently sabotage it. Opti
 mization passes\, designed to make code faster\, can introduce timing leak
 s\, violating security guarantees in ways developers never intended. But w
 hich optimizations are responsible? And how can you stop them without rewr
 iting the compiler itself?\n\nIn this talk\, we investigate the mystery be
 hind compiler-induced constant-time violations. We analyze real-world exam
 ples from GCC and LLVM\, exposing how specific optimizations betray securi
 ty assumptions. More importantly\, we provide practical solutions: which c
 ompiler flags can mitigate these leaks\, and what is the real cost of secu
 ring your compiled code?\n\nYour compiler may not be your friend—but wit
 h the right knowledge\, you can stop it from turning against you.
DTSTAMP:20260512T153429Z
LOCATION:Amphitheater 122
SUMMARY:Fun with flags: How Compilers Break and Fix Constant-Time Code - An
 toine Geimer
URL:https://cfp.pass-the-salt.org/pts2025/talk/RDEFF3/
END:VEVENT
END:VCALENDAR