“We’re aware of reports that access to Signal has been blocked in some countries,” Signal says. If you are affected by the blocks, the company recommends turning on its censorship circumvention feature. (NetBlocks reports that this feature lets Signal “remain usable” in Russia.)

  • Andromxda 🇺🇦🇵🇸🇹🇼@lemmy.dbzer0.comEnglish
    41·
    3 months ago

    Signal having the server code closed source for more than a year so the Signal devs could get a headstart and insider knowledge

    That argument makes absolutely no sense. This server-side code does almost nothing. The only task it really has is passing around encrypted packets between clients. All of the encryption is client-side, of course including metadata encryption. That’s how end-to-end encryption works. The server code really doesn’t matter. The Signal protocol, which is used for client-side, local, on-device end-to-end encryption has always been fully open, and it can be used by any app/platform.

    How one can trust Signal after them showcasing what they truly stand for is mind blowing

    It’s very simple. The client is open source, and the encryption happens locally within the client application. You don’t need to trust anything or anyone except for the code and mathematics, which are fully open, so you can verify them yourself.

    It’s mind-boggling how people attempt to spread so much misinformation while having absolutely no understanding of the topic their talking about.

    • barryamelton@lemmy.ml
      11·
      3 months ago

      That argument makes absolutely no sense. These server-side code does almost nothing. The only task it really has is passing around encrypted packets between clients.

      So it knows about all metadata, plus registration with phone number, etc. got it.

      The Signal protocol, which is used for client-side, local, on-device end-to-end encryption has always been fully open, and it can be used by any app/platform.

      you conveniently leave out how you need to use the client built by Signal, with dependencies from Google Services and the like, and you can’t use one built from the source they provide. Which at that point means they can introduce whatever they want in whichever version.

      Decentralisation is the only safe way.

      • fira959@lemmy.mlEnglish
        1·
        3 months ago

        You can use reproducible builds to verify that the provided clients are the result of the source code and you can also use alternative clients like Molly

      • Andromxda 🇺🇦🇵🇸🇹🇼@lemmy.dbzer0.comEnglish
        21·
        3 months ago

        So it knows about all metadata

        Metadata is encrypted on the client-side using Signal’s sealed sender implementation. The client also removes as much metadata as possible. All of this is open-source and happens in the client application.

        plus registration with phone number

        Signal doesn’t store phone numbers. It derives a user id from your phone number along with other parameters. It’s in the open-source server code, you can check it out yourself.

        you need to use the client built by Signal

        No you don’t. I myself use a fork of Signal called Molly.

        with dependencies from Google Services and the like

        Not true again. You don’t need to use the official binary that includes Google libraries. These aren’t required for the app to function. You can use Signal-FOSS or Molly-FOSS, and it works just fine.

        and you can’t use one built from the source they provide

        If this was true, forks like Signal-FOSS or Molly wouldn’t exist.

        Which at that point means they can introduce whatever they want in whichever version.

        Stupid conclusion, because all of your previous points are false

        Stop spreading false information, focus on the facts.