conv.

All stories
SecurityQuiet 10d · day 12

Signal fork Molly goes unpatched three months after an exploit fix in Signal 8.27

A Hacker News/Lemmy post warns that the privacy-hardened Signal fork Molly remains vulnerable to an October exploit that mainline Signal already patched.

What to know

  • Molly, a hardened Signal fork popular on de-Googled Android phones, has gone three months without an update and lacks the fix for an October exploit that Signal itself patched in version 8.27.
  • The original post urges users to uninstall Molly and switch to mainline Signal until it resumes updates.
  • Commenters explain they stick with Molly for features missing from mainline Signal, such as UnifiedPush notifications on phones without Google Play Services.
  • The thread broadens into criticism of both F-Droid's slow publishing process and Signal's own Play Store-centric distribution, including its self-updating APK and lack of reproducible builds.

The dispute Whether the fault for stale, vulnerable forks lies with the fork maintainers themselves, with F-Droid's slow review process, or with Signal's restrictive official distribution. · positions read across 29 posts and comments

many voices

People keep running Molly despite the risk because it offers features mainline Signal lacks, like UnifiedPush and de-Googled compatibility.

  • “I’m running it specifically for the UnifiedPush support which gives me push notifications without Google Play Services.”

    HN commenter · Hacker News ↗
some voices

Signal itself is to blame for pushing users toward forks by relying on Play Store distribution and a cursed self-updating APK instead of proper reproducible builds.

  • “I seriously don’t understand how signal is only on the PlayStore”

    HN commenter · Hacker News ↗
some voices

F-Droid's own publishing process is slow and frustrating, which likely explains delays like Molly's.

  • “My app went 3 months without being updated there because of how they manage things. They are way way way way. Way too frustrating to deal with.”

    HN commenter · Hacker News ↗

Molly developers Maintainers of the Molly Signal forkSignal Upstream secure messaging app makerF-Droid Open-source Android app repositoryDeepLogin Poster who raised the alarm

How it unfolded 1 development · click the chart to see its coverage articlesposts

Peak 13 pieces in 3h at Oct 31, 5 AM; 36 pieces over 12 days (2 articles · 6 posts · 28 comments) Oct 31, 5 AM — 13 pieces · 2 articles · 2 posts · 9 comments — Hacker News 10, Newswires 2, Mastodon 1Oct 31, 8 AM — 9 pieces · 2 posts · 7 comments — Hacker News 7, Mastodon 2Oct 31, 11 AM — 7 pieces · 1 post · 6 comments — Hacker News 6, Mastodon 1Oct 31, 2 PM — 4 pieces · 1 post · 3 comments — Hacker News 3, Mastodon 1Oct 31, 5 PM — 1 piece · 1 comment — Hacker News 1Oct 31, 8 PM — 1 piece · 1 comment — Hacker News 1Oct 31, 11 PM — quietNov 1, 1 AM — quietNov 1, 4 AM — quietNov 1, 7 AM — quietNov 1, 10 AM — quietNov 1, 1 PM — 1 piece · 1 comment — Hacker News 1Nov 1, 4 PM — quietNov 1, 7 PM — quietNov 1, 10 PM — quietNov 2, 1 AM — quietNov 2, 4 AM — quietNov 2, 7 AM — quietNov 2, 10 AM — quietNov 2, 1 PM — quietNov 2, 4 PM — quietNov 2, 7 PM — quietNov 2, 10 PM — quietNov 3, 1 AM — quietNov 3, 4 AM — quietNov 3, 7 AM — quietNov 3, 10 AM — quietNov 3, 1 PM — quietNov 3, 4 PM — quietNov 3, 7 PM — quietNov 3, 10 PM — quietNov 4, 1 AM — quietNov 4, 4 AM — quietNov 4, 7 AM — quietNov 4, 10 AM — quietNov 4, 1 PM — quietNov 4, 4 PM — quietNov 4, 7 PM — quietNov 4, 10 PM — quietNov 5, 1 AM — quietNov 5, 4 AM — quietNov 5, 7 AM — quietNov 5, 10 AM — quietNov 5, 1 PM — quietNov 5, 4 PM — quietNov 5, 7 PM — quietNov 5, 10 PM — quietNov 6, 1 AM — quietNov 6, 4 AM — quietNov 6, 7 AM — quietNov 6, 10 AM — quietNov 6, 1 PM — quietNov 6, 4 PM — quietNov 6, 7 PM — quietNov 6, 10 PM — quietNov 7, 1 AM — quietNov 7, 4 AM — quietNov 7, 7 AM — quietNov 7, 10 AM — quietNov 7, 1 PM — quietNov 7, 4 PM — quietNov 7, 7 PM — quietNov 7, 10 PM — quietNov 8, 1 AM — quietNov 8, 4 AM — quietNov 8, 7 AM — quietNov 8, 10 AM — quietNov 8, 1 PM — quietNov 8, 4 PM — quietNov 8, 7 PM — quietNov 8, 10 PM — quietNov 9, 1 AM — quietNov 9, 4 AM — quietNov 9, 7 AM — quietNov 9, 10 AM — quietNov 9, 1 PM — quietNov 9, 4 PM — quietNov 9, 7 PM — quietNov 9, 10 PM — quietYesterday, 1 AM — quietYesterday, 4 AM — quietYesterday, 7 AM — quietYesterday, 10 AM — quietYesterday, 1 PM — quietYesterday, 4 PM — quietYesterday, 7 PM — quietYesterday, 10 PM — quietToday, 1 AM — quietToday, 4 AM — quietToday, 7 AM — quietToday, 10 AM — quietToday, 1 PM — quietToday, 4 PM — quiet 1
Nov 1Nov 2Nov 3Nov 4Nov 5Nov 6Nov 7Nov 8Nov 9yesterdaynow · 7:49 PM ET
  1. 1

    Commenters criticize Signal's Play Store-centric distribution

    Other commenters turn the criticism back on Signal itself, faulting it for lacking a reproducible, blob-free build on F-Droid or Flathub and instead relying on a self-updating APK and an AppImage on Linux.

    “It is really bad of Signal to not have a blobfree reproducible build on F-Droid and Flathub, or even just external repos (for F-Droid and flathub).”
    — HN commenter
    • The incorporated 501c3 named Signal is, in IT terms, a vendor. Is it not?The Signal client software is open source and some of the clients have reproducible builds. The Signal server software is open source, though has a history of being over a year out of date at some points. Other deployments of this server software for production use are…

      jon128Hacker News11d agoview on Hacker News ↗
    2 more of the top 3 · 29 posts in this stretch
    • thomholwerda@exquisite.social

      Uh, perhaps don't use Molly, the Signal fork? https:// piefed.world/c/ysk/p/1503393/y sk-molly-signal-fork-has-not-been-updated-since-3-months-and-is-vulnerable-to-attacks-f

      thomholwerda@exquisite.socialMastodon11d agoview on Mastodon ↗
    • It explains perfectly why Signal does not want third-party clients.To the haters: I am not saying that it is perfect, in an ideal world we could have secure third-party clients. I am just saying that it is pragmatic: in our world, we don't.Signal has forever been a pragmatic approach to private messaging, and it succeeded at that: Signal literally…

      palataHacker News11d agoview on Hacker News ↗
    all of them →
  2. background

    Developer blames F-Droid's process for update delays — A commenter identifying as an Android developer with an app on both Play Store and F-Droid says F-Droid's publishing process is so slow and frustrating that it has caused months-long update gaps for their own app, suggesting similar friction could explain Molly's lag.

  3. background

    Users defend Molly for UnifiedPush and de-Googled setups — Commenters explain they keep running Molly specifically for UnifiedPush notifications and compatibility with GrapheneOS phones that lack Google Play Services, despite the security risk.

  4. background

    Post flags Molly's three-month update gap as a security risk — A cross-post from PieFed's 'ysk' community reaches Hacker News, arguing Molly remains vulnerable and urging users to switch to mainline Signal and delete Molly until it resumes updates. The post reaches 102 points and 61 comments on HN.

  5. background

    Exploit disclosed and patched in Signal 8.27 — An exploit affecting Signal protocol clients was disclosed in October and fixed by Signal in version 8.27, but the Molly fork did not receive the corresponding fix.

Also covered reported alongside — the timeline has no entry for these yet

  1. first by HN Best, 11d ago · also HN Frontpage

What people are saying 21 voices from 1 site · best of 29 · verbatim

Still unanswered
  • Is Molly actually abandoned, or will it resume updates?
  • Why doesn't Signal publish a blob-free reproducible build on F-Droid or Flathub itself?