Ethnography proposes 'exists' statements, not 'for all' statements #realworldcrypto
Coffee time #realworldcrypto
'Defending the Open Internet: TLS, Passkeys, and the Privacy Stakes of Digital Identity', by Christopher Harrell #realworldcrypto
Q: How do I resolve the dilemma that if i work on this, governments will use it to discriminate [against children, women, etc] A: Build primitives that work with trust lists, group of issuers we trust [um we trusted the US until we didn't, oops] #realworldcrypto
Q: Device-bound means i lose my creds A: Cloud-based HSM [narrator: 🙄] #realworldcrypto
Not all have PQ privacy #realworldcrypto
Q: The nice ZKs going to PQ change the computational/privacy properties A: Depending on the construction (BLS vs ML-DSA, relying on the symmetric guts of certain constructions) #realworldcrypto
Next up, 'Zero Knowledge (About) Encryption: On the Security of Cloud-based Password Managers', presented by Matteo Scarlata and Giovanni Torrisi #realworldcrypto
'E2EE' password managers #realworldcrypto
We don't trust the server, should only have access to the vault plaintext if you have access to the master password #realworldcrypto
features ('features') that lead to this breakdown: #realworldcrypto
oh recovery flows #realworldcrypto
Partial vault sync (😭) #realworldcrypto
Relatedly, icon fetching ('metadata') #realworldcrypto
Sharing items #realworldcrypto
backwards compatibility leads to attacks 😭 #realworldcrypto
Heisenberg Attack: 'nothing to do with Breaking Bad, although we're gonna break it pretty badly 😈' #realworldcrypto
Ways to mitigate security issues in these risky features: key transparency, better designs for key recovery #realworldcrypto
SAY IT AGAIN #realworldcrypto
Better protections against downgrade attacks #realworldcrypto
No time for Q's, aw Next up, 'Improving Account Security for Victims of Account Compromise through Client-Side Access Logging', presented by Carolina Ortega Pérez and Paul Gerhart #realworldcrypto
Trying to help victims of intimate partner violence experiencing tech abuse #realworldcrypto
Easy to spoof user agents #realworldcrypto
Need OS support #realworldcrypto
PK-CSAL still has to worry about ghost users #realworldcrypto
If we sync keys we can prevent ghost users #realworldcrypto
password-based key sync #realworldcrypto
Extension to WebAuthN (just changing a label) #realworldcrypto
Do need OS support #realworldcrypto
Q: Pubkey for each device, does that not act like a device id, impact on privacy? A: Actually different keys for different sessions #realworldcrypto
Next up, 'Efficient Threshold ML-DSA', presented by Sofia Celi and Thomas Espitau #realworldcrypto
#️⃣ lattices #️⃣ #realworldcrypto
First an ID protocol, slap some Fiat-Shamir on it, signatures?? #realworldcrypto
[oop that's not committing to the public verification key] #realworldcrypto
Combining shares/signing shares #realworldcrypto
Really want th-ML-DSA signatures to be exactly compatible with singleton ML-DSA verification #realworldcrypto
How to handle the ML-DSA rejection sampling #realworldcrypto
Must not be able to distinguish between th-ML-DSA and singleton ML-DSA bc the sampling distributions between them are different #realworldcrypto
2 offline, 4 online rounds, first is independent of the message, allows pre-processing, safe for concurrency #realworldcrypto
May be useful in modern internet applications #realworldcrypto
Look at this beautiful arrrrt #realworldcrypto
Q: Identifiable abort? A: Not this construction, there are options but they break other things #realworldcrypto
Next up, 'XHMQV: Better Efficiency and Stronger Security for Signal's Initial Handshake based on HMQV', presented by Rune Fiedler #realworldcrypto
XHMQV: Better Efficiency and Stronger Security for Signal’s Initial Handshake based on HMQV

The Signal protocol is the most widely deployed end-to-end-encrypted messaging protocol. Its initial handshake protocol X3DH allows parties to asynchronously derive a shared session key without the need to be online simultaneously, while providing implicit authentication, forward secrecy, and a form of offline deniability. The X3DH protocol has been extensively studied in the cryptographic literature and is acclaimed for its strong "maximum-exposure" security guarantees, hedging against compromises of users' long-term keys and medium-term keys but also the ephemeral randomness used in the handshake. This maximum-exposure security is achieved by deriving keys from the concatenation of 3–4 Diffie–Hellman (DH) secrets, each combining two long-term, medium-term, or ephemeral DH shares. Remarkably, X3DH's approach of concatenating plain DH combinations is sub-optimal, both in terms of maximum-exposure security and performance. Indeed, Krawczyk's well-known HMQV protocol (Crypto '05) is a high-performance, DH-based key exchange that provides strong security against long-term and ephemeral key compromise. One might hence wonder: why not base Signal's initial handshake on HMQV? In this work, we study this question and show that a carefully adapted variant of HMQV, which we call XHMQV, indeed enables stronger security and efficiency while matching the constraints of Signal's initial handshake. Most notably, HMQV does not work as a drop-in replacement for X3DH, as the latter's asynchronicity requires the protocol to handle cases where one party runs out of ephemeral keys (pre-uploaded to the Signal server). Our XHMQV design hence augments HMQV with medium-term keys analogous to those used in X3DH. We prove that XHMQV provides security in all 3–4 compromise scenarios where X3DH does and additionally in 1–2 further scenarios, strengthening the handshake's maximum-exposure guarantees while using more efficient group operations. We further confirm that our XHMQV design achieves deniability guarantees comparable to X3DH. Our security model is the first to capture Signal's long-term key reuse between DH key exchange and signatures, which may be of independent interest.

IACR Cryptology ePrint Archive
Classic X3DH #realworldcrypto
Sometimes you run out of prekeys and have to reuse one, this is 'reduced mode' #realworldcrypto
Everything old is new again #realworldcrypto
More efficient, one less group exponentiation, stronger maximum exposure, but still doesn't help with exhaustion of prekeys #realworldcrytpo
Add in the semi-static prekeys #realworldcrypto
Bounds for XHMQV key indistinguishability #realworldcrypto