• possibly a cat@lemmy.ml
    link
    fedilink
    arrow-up
    4
    ·
    1 year ago

    In this sense it wouldn’t directly have an adverse effect on end-to-end encryption.

    imo E2EE includes the environment in its scope as a complete product, and I don’t see how this can be executed without weakening the environment’s security.

    • sunbeam60@lemmy.one
      link
      fedilink
      arrow-up
      6
      ·
      1 year ago

      I’m deeply against this ridiculous proposal.

      But scanning of messages already happens, tbf, for spell checking, emoji replacement, links to known infectious sites.

      Photo copiers do client side scanning to prevent copying of money.

      There are precedents.

      I hate this proposal. But let’s be straight about the facts: The phone has full access to everything you send and receive already. This isn’t the same as having an encryption back door.

      • possibly a cat@lemmy.ml
        link
        fedilink
        arrow-up
        7
        ·
        1 year ago

        There are precedents, but we can forego these if we want. I don’t have to use Google’s keyboard. I can even degoogle my phone with Graphene OS. Some black boxes remain of course but they are small and relatively secure. Meanwhile a client-side scanner is adding an unavoidable increase to the attack surface. That’s a weakened security environment. And not just for your cat videos, but for journalists and others dealing with sensitive materials.

        I can’t wait to see how many horrible implementations devs come up with because this feature provides no value for their employers.