Key Exchange Flaws: Why Crypto Theorist iltg Slams Proposed E2EE as 'Application-Specific Circus'
The core technical debate revolves around whether proposed standards like MLS can achieve true, end-to-end encryption across the entire decentralized web or if they only function within limited, application-specific silos. The mechanism itself—secure out-of-band public key exchange—is identified as the primary unsolved hurdle, not the encryption layer itself.
Those skeptical of the crypto proposals point out serious vulnerabilities. iltg argued vehemently that intermediate servers can manipulate the key exchange, meaning E2EE only works between users of a specific front-end like Emissary, not across the whole Fediverse. Steve cut through the noise, asserting that true federation relies on protocols like Matrix, not just the convenience of a single app's DM function. Meanwhile, regarding RCS, d0ntpan1c stated that Apple's testing merely confirms Google's initial infrastructure lock-in, not a systemic protocol breakthrough.
The raw assessment is that the technical complexity of validating trust outweighs the current cryptographic drafts. Consensus demands external, trusted channels for key verification to prevent server-side key manipulation. The fault lines are clear: proponents see future adoption of standards like MLS; critics see localized, easily undermined fixes.
Key Points
MLS drafts fail to guarantee encryption across the entire Fediverse.
iltg warned that server manipulation of the key exchange process confines encryption to specific client applications, not the network backbone.
Federation stability relies on underlying protocols, not single-app features.
Steve argued that protocols like Matrix define federation capability, dismissing reliance on DMs.
Apple's RCS tests do not signal true interoperability.
d0ntpan1c argued that RCS remains bound by Google's server infrastructure and carrier agreements, regardless of Apple's testing.
Solving key exchange trust requires external verification mechanisms.
iltg stressed that merely using public keys is insufficient; servers can lie about or proxy keys, demanding an out-of-band validation channel.
Source Discussions (3)
This report was synthesized from the following Lemmy discussions, ranked by community score.