374
Hacker plants false memories in ChatGPT to steal user data in perpetuity (arstechnica.com)
submitted 2 years ago by to c/technology@lemmy.world
35 comments fedilink hide all child comments
you are viewing a single comment's thread
view the rest of the comments
[–] 11 points 2 years ago (1 child)

IME they usually proxy and/or prefetch images for caching instead of blocking them. Only spam content is blocked by default.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 6 points 2 years ago (1 child)

    This wouldn't help, would it? How would you prefetch and cache:

    site.com/base64u-to-niceware-word-array/image.gif

    ? It would look like a normal image URL in any article, but actually represent data.

    Note: "niceware" is a way to convert binary or text data into a set of words like "cow-heart-running-something-etc".

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 4 points 2 years ago (3 children)

    If it’s prefetched, it doesn’t matter that you reveal that it’s been “opened,” as that doesn’t reveal anything about the recipient’s behavior, other than that the email was processed by the email server.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 6 child comments
    •
  • [–] 3 points 2 years ago (1 child)

    Personally speaking, I’ve never been a fan of this method because to the hosting web server it was still fetched. That might confirm that an email address exists or (mistakenly) confirm that the user did in fact follow the link (or load the resource).

    I have ad and tracking blocked like crazy (using DNS) so I can’t follow most links in emails anyway. External assets aren’t loaded either, but this method basically circumvents that (which I hate).

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 2 points 2 years ago (1 child)

    If by prefetch you mean the server grabs the images ahead of time vs the client, this does not happen, at least on amy major modern platform that I know of. They will cache once a client has opened, but unique URLs per recipient are how they track the open rates.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 1 point 2 years ago (1 child)

    But the path changes with every new data element. It's never the same, so every "prefetch" is a whole new image in the system's eyes.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 2 points 2 years ago (1 child)

    Even with a unique link, if the behavior is that as soon as the email server receives it, it’s prefetched, what does that reveal about the user?

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 1 point 2 years ago* (1 child)

    Server or client, every supposed prefetch would be unique. If I trick an LLM client into grabbing:

    site.com/random-words-of-data/image.gif

    Then:

    site.com/more-random-data/image.gif

    Those are two separate images to the cache engine. As the data refreshes, the URL changes, forcing a new grab each time.

    For email, marketers do this by using a unique image URL for every recipient.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 1 point 2 years ago (1 child)

    Cool, all of your images are getting fetched by the server as it receives and processes the emails. You have 100% open rate on all emails to that domain within 3 minutes of send.

    What do you know about the user and their behavior? Nothing. The prefetch is not tied to their actions, therefore you cannot learn anything about their actions.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •