• rrobin@lemmy.world
    link
    fedilink
    arrow-up
    22
    ·
    1 year ago

    This is a really nice summary of the practical issues surrounding this.

    There is one more that I would like to call out: how does this client scanning code end up running in your phone? i.e. who pushes it there and keeps it up to date (and by consequence the database).

    I can think of a few options:

    1. The messaging app owner includes this as part of their code, and for every msg/image/etc checks before send (/receive?)
    2. The phone OS vendor puts it there, bakes it as part of the image store/retrieval API - in a sense it works more on your gallery than your messaging app
    3. The phone vendor puts it there, just like they already do for their branded apps.
    4. Your mobile operator puts it there, just like they already do for their stuff

    Each of these has its own problems/challenges. How to compel them to insert this (ahem “backdoor”), and the different risks with each of them.