Parallel Reconstruction of Lawful TLS Wiretapping

Secret web snooping drama has commenters fighting over who really dropped the ball

TLDR: A new write-up shows how “secure” web connections may still be secretly intercepted, and a likely renewal mistake may have blown the cover on it. Commenters were split between panic, fact-checking the framing, and roasting the sloppy security habits that may have made it possible.

The big reveal here isn’t just that encrypted web traffic can still be secretly intercepted under the right conditions — it’s that the internet comment section instantly turned into a full-blown detective show. The article walks through how a 2023 incident involving jabber.ru may have worked, including the deliciously embarrassing detail that a surveillance setup may have exposed itself because someone seemingly forgot to renew a certificate. Yes, the digital equivalent of a spy tripping over their own shoelaces.

And the community? Oh, they were not content to just gasp and move on. One camp went straight to outrage: wait, can companies that sell “lawful intercept” tools really crack supposedly secure browsing? Another camp slammed the framing itself, basically yelling, “Hold on — don’t turn this into a conspiracy movie if the evidence points somewhere else.” That sparked the juiciest fight in the thread: was this a shocking case of high-level collusion, or just a more ordinary but still scary case of traffic being rerouted and certificates being issued the “normal” way?

Then came the nerdier pile-on. Some readers asked why Certificate Transparency — a public logging system meant to catch suspicious website certificates — didn’t save the day. Others used the moment to roast bad security habits, especially the all-too-common “just run it as admin” approach. The vibe was half alarm, half smug post-mortem, with a strong side of “this is terrifying… and also kind of hilarious.”

Key Points

  • The article states that TLS wiretapping with root-CA-signed certificates is a documented reality and cites a 2023 interception case targeting jabber.ru.
  • The cited case involved encrypted traffic interception on infrastructure associated with Hetzner and Linode.
  • The article says the 2023 incident became visible after a TLS certificate used in the operation was apparently not renewed, producing browser warnings.
  • A timeline highlighted in the article notes that an unknown actor began issuing SSL/TLS certificates on 18 April 2023.
  • The article identifies ACME and the acme.sh client as important technical elements because acme.sh was running on the jabber.ru server to automate certificate renewals.

Hottest takes

"What LI vendors can break https?" — TZubiri
"Maybe what people get upset about is catchy misleading summaries" — perching_aix
"Its a shame this is still taught in the 'just run as admin' style" — edelbitter
Made with <3 by @siedrix and @shesho from CDMX. Powered by Forge&Hive.