• gila@lemm.ee
    link
    fedilink
    English
    arrow-up
    9
    ·
    edit-2
    10 months ago

    If you’re using these links as restaurant menus as opposed to ordering platforms (this is how I use them, and how this post & other commenters seem to be presenting the concept) that’s kind of limited to a risk of straight up being phished in a situation where you don’t really have any reason to hand over your information.

    In a pub/bar setting it’s helpful to know what’s available at the bar before I’m standing at it, especially if I’m buying a round. That is to say it generally lowers the bar to menu availability, not raise it. Because before the pub/bar would simply have no table menu and you’d figure out what you wanted by asking or looking at the taps

    • Cypher@lemmy.world
      link
      fedilink
      English
      arrow-up
      15
      ·
      10 months ago

      There are clickless exploits and other methods that don’t require you to enter information, nevermind that nearly all of these menus have ordering and payment available through them and mimicking websites is fairly simple.

      QR codes cannot be trusted just like links from unknown sources cannot be trusted.

      • gila@lemm.ee
        link
        fedilink
        English
        arrow-up
        6
        ·
        10 months ago

        I think you’ll find there isn’t an Android or iPhone on the market today vulnerable to SQL injection or XSS etc via scanning a QR code. You’re talking about device vulnerabilities that get patched and it’s equally possible to encounter these exploits with plaintext URLs

        • Cypher@lemmy.world
          link
          fedilink
          English
          arrow-up
          8
          ·
          10 months ago

          You’re talking about device vulnerabilities that get patched

          Patching out zero days takes time.

          it’s equally possible to encounter these exploits with plaintext URLs

          Yes which is why I clearly stated that following URLs from any unknown sources carries risk.

          The difference is that due to menus being a point of payment they have a greater incentive for abuse.

          • gila@lemm.ee
            link
            fedilink
            English
            arrow-up
            8
            ·
            10 months ago

            So we shouldn’t use smartphone features if they could potentially have exploits? With this logic you shouldn’t have a phone.

        • Arcka@midwest.social
          link
          fedilink
          English
          arrow-up
          4
          ·
          10 months ago

          If the restaurant doesn’t have a good enough reputation that I couldn’t trust the QR they provided (which displays the URL so I can inspect it before launching the web browser), I also wouldn’t want to trust my health to eating there.

          It isn’t like some random thing you found on the sidewalk.

          • gila@lemm.ee
            link
            fedilink
            English
            arrow-up
            4
            ·
            10 months ago

            I’m pretty sure these are just an echo of the same concerns people put forward when URLs first started being included in signage, due to general privacy/security concerns with the internet. Somehow we got through it!