Warrant canaries in practice: why the signature matters more than the words
In a coal mine, the canary dies quietly and every miner knows exactly what that means. On the internet, a missing quarterly statement is supposed to work the same way for secret surveillance orders. Whether it actually does depends less on the words than on a cryptographic signature most users never check.
The coal mine logic
A warrant canary is a regularly published statement that a service provider has not received legal process it would be forbidden to mention, such as a National Security Letter or a FISA order. When such an order arrives, the gag attaches, and the provider simply stops repeating the statement. Readers infer receipt from the silence. The legal theory leans on compelled speech doctrine: a court can force someone to stay quiet, but forcing them to lie is another matter entirely. The Electronic Frontier Foundation laid out this reasoning in its canonical FAQ, noting that no law prohibits reporting the legal process you have not received (eff.org). No US court has yet ruled directly on the question. The theory remains elegant, untested, and load-bearing.Lavabit: silence as a signal
The genre has a founding trauma. In August 2013, encrypted email provider Lavabit, then used by Edward Snowden, abruptly suspended operations rather than hand over its SSL keys, with owner Ladar Levison writing that he was barred from explaining why (Wired). His closing advice was blunt: do not trust private data to companies with physical ties to the United States. Lavabit never published a formal canary, but the episode demonstrated the mechanism. By shutting down his own infrastructure, Levison transmitted information he was legally forbidden to put into sentences. Kevin Poulsen's contemporaneous reporting told readers to read between the lines, and they did. The shutdown itself was the message.Apple's vanishing line
Apple became the highest-profile corporate adopter in November 2013, when its transparency report declared that it had never received an order under Section 215 of the USA Patriot Act (Ars Technica). The statement carried no cryptographic signature and no explicit promise to keep publishing it. Those omissions mattered. When the line failed to appear in two subsequent reports in September 2014, observers speculated that Apple had been served. It was almost certainly a false alarm caused by reformatting. As the Harvard Journal of Law & Technology has documented, because Apple never clearly designated the statement as a canary, its disappearance generated suspicion rather than information (Harvard JOLT). Ambiguity killed the signal.Failures nobody planned for
Real canaries die of mundane causes more often than legal ones. The Riseup collective missed a scheduled canary update in 2016 amid sealed court proceedings, and when the canary returned it no longer asserted the absence of gag orders. Canarywatch, the EFF-backed monitoring project launched in 2015, stopped tracking canaries within eighteen months, citing how non-standard formats made automated checking impractical. The Yale Law Journal's analysis of canaries warns that a government served with a secret order might simply compel the provider to keep publishing the now-false statement, producing a so-called zombie canary (Yale L.J.). A dead canary is therefore ambiguous by design flaws, not just by intent. Silence can mean a subpoena, a vacationing sysadmin, or a bankrupt company.Why the signature is the story
This is where cryptography earns its keep. An unsigned canary on a web server can be edited or forged by anyone who controls that server, including a compromised host or a coerced administrator. rsync.net, which pioneered the commercial canary in 2006 and still publishes weekly, signs each statement with a long-standing public key and embeds news headlines and sports scores as freshness anchors proving the text postdates prior editions (rsync.net). The signature delivers two guarantees at once: authenticity, meaning the named key holder produced the text, and integrity, meaning nothing altered it afterward. Neither survives without the other. Providers typically generate these signed statements themselves using tools like our PGP sign tool, while readers confirm them with the PGP verify tool against a fingerprint archived in multiple independent locations. If the key itself can be swapped unnoticed, everything collapses.A canary that is not cryptographically signed is theatre. The signature is what makes the absence meaningful.
How to read one responsibly
A disciplined reading treats a canary as evidence, not gospel. Before drawing conclusions from any provider's statement, check the fundamentals:- Is the text clearsigned, and does it verify against a well-known public key?
- Does the fingerprint match copies held off-site, in archives, and on keyservers?
- Are there freshness anchors, such as dated headlines or blockchain hashes?
- Has the wording narrowed between editions, removing specific denials?
- Did the publisher explain a lapse, or go silent about the silence?