Dilroop Ummar Shameem
I’m a Systems & Cryptography Engineer with a background in Political Science and Esports, which shaped my research mindset. I started as a Python backend engineer working with Django, APIs, and application architecture, then gradually shifted toward security, systems, and cryptography to understand how software behaves beneath the surface. Today, I work mainly with Rust, along Python with and C++, focusing on protocol experiments, cryptography, and security-oriented systems.
Session
An organisation enables hybrid post-quantum TLS and its monitoring dashboard continues to show successful TLS 1.3 connections. But did those connections use X25519MLKEM768 or classical X25519? Did the hybrid attempt fail before an application retried classically? Did a proxy terminate the external connection and hide the negotiated group from the backend? Most ordinary TLS logs cannot answer these questions.
This talk examines three connections that produce the same “TLS succeeded” event while reaching different security outcomes: successful hybrid negotiation, intentional classical negotiation, and a failed hybrid attempt followed by a classical retry.
Using prepared OpenSSL output, packet-trace excerpts, log comparisons and protocol diagrams, the session explains the difference between required, attempted, negotiated and final cryptographic state. It then presents a practical event model for recording the selected group, runtime provider, failure category, retry decision and policy result.
Attendees will learn how to verify whether PQC is actually being used, detect silent classical exceptions and define migration success through policy satisfaction rather than connection success. No live demonstration, quantum-computing theory or lattice mathematics is required.