Signal adds an extra layer of security to make sure you’re actually chatting with the right person
Signal has introduced Automatic Key Verification (AKV), a new feature designed to protect against man-in-the-middle attacks in which someone could intercept encrypted messages by tampering with the app's central directory of user accounts. The update matters because Signal is widely relied upon by diplomats, activists and journalists for secure communication, and while its end-to-end encryption already scrambles messages, a compromised directory could previously have redirected encrypted chats to the wrong recipient without users noticing.
AKV lets users tap "Verify automatically" on a contact's "View Safety Number" screen to get a green checkmark confirming their public encryption key matches what Signal's new key transparency system expects. Behind the scenes, Signal logs every account change, such as a new phone number, into a cryptographic ledger and index, which it checks on the user's behalf; independent auditors Cloudflare and Trail of Bits verify that this ledger itself hasn't been tampered with, though a monitoring step is still needed to confirm the underlying data is accurate. One notable limitation is that the feature currently requires having a contact's phone number.
In short
- Signal launches Automatic Key Verification to block man-in-the-middle attacks
- Users get a one-tap green checkmark confirming a contact's encryption key
- Cloudflare and Trail of Bits independently audit Signal's new key ledger
Steelman: both sides, in good faith
The strongest fair case each way — we don't pick a winner.
The case for
Signal has implemented a necessary security improvement that protects vulnerable users like journalists and activists from sophisticated man-in-the-middle attacks targeting the directory infrastructure. The key transparency system, with independent verification from established security firms, employs sound cryptographic principles without requiring users to perform complex manual verification. This represents responsible security engineering that meaningfully enhances protection for populations facing genuine threats.
The case against
Whilst addressing a specific vulnerability, this feature introduces new centralised dependencies and logging of account changes that may conflict with privacy principles of minimising institutional data and trust requirements. The system's complexity could foster false confidence in security mechanisms users don't fully understand, and more decentralised approaches to key verification might better align with Signal's foundational commitment to user privacy and minimal data collection.
Explained simply
Signal is a messaging app that uses end-to-end encryption: messages are scrambled so only the people in a conversation can read them. To set up an encrypted chat, the app also needs to match each account with the right public encryption key.
That matching matters because a central directory holds information about Signal accounts. If someone tampered with it, a chat could be directed to a different key, potentially allowing an outsider to intercept messages without either user noticing.
Signal is used by people including diplomats, activists and journalists, so confidence that messages reach the intended person is important. Its safety numbers let contacts check their keys, while newer systems can help detect changes to account information; these checks still depend on the information being accurate.