cross-posted from: https://piefed.world/c/ysk/p/1503393/ysk-molly-signal-fork-has-not-been-updated-since-3-months-and-is-vulnerable-to-attacks-f

As of now, Molly lastest release was in 31 July (Version v8.19.2-4).

It contains vulnerabilities that had been simply fixed in mainline Signal.

Take for example the latest exploit disclosed in October, it has been fixed in Signal 8.27. 1. Meanwhile Molly remains vulnerable.

It's currently recommended to use mainline Signal and delete Molly till they at least return to updating their app adequately, if they ever will.

you are viewing a single comment's thread
view the rest of the comments
[–] 6 points 1 day ago (7 children)

That sucks. Does the original Signal app deliver notifications properly without Play Services?

  • source
  • hideshow 7 child comments
  • [–] 8 points 1 day ago (1 child)

    I'm new to GrapheneOS and running Signal without anything configured with the word Google in it. I am receiving notifications just fine.

  • source
  • parent
  • hideshow 1 child comment
  • [–] 1 point 1 day ago* (last edited 1 day ago)

    That depends on where you got the APK from

    • the playstore apk only supports FCM
    • the standalone, hidden (you only find it via search engines), apk on their website also supports websocket
    • Twinhelix Signal-FOSS only supports websocket
    • molly also supports blobfree FCM and UnifiedPush

    But note that UnifiedPush is not supported by signal, so you need to register a fake device on a server running MollySocket. Which is very much additional attack surface and only worth it if you really rarely use signal

  • source
  • parent
  • [–] 6 points 1 day ago (2 children)

    The APK from Signal's website doesn't require Play services, just don't install Signal via Play Store. DaNgEr ZoNE eye rolls aside:

    https://signal.org/android/apk

    Annoying, I rather liked Molly.

  • source
  • parent
  • hideshow 2 child comments