• Caedarai@reddthat.com
    link
    fedilink
    arrow-up
    0
    ·
    2 days ago

    Well, because it won’t be signed by a trusted CA for that task. Like if CAs had a category of certificate issuance that applied here (the standardisation issue) then it would be easy to spot a fake (which wouldn’t be correctly signed). Alternatively, you could take the European approach of having everything government related (like public street parking, though Europe mostly uses apps for that, not signed QR codes) rely on government entities and those in turn on a national set of government CAs.

      • Caedarai@reddthat.com
        link
        fedilink
        arrow-up
        0
        ·
        1 day ago

        QR codes are mostly meant to let you get an amount of info (they’re mostly text-based) without having to type or enter it manually when you might make mistakes or when the process is just faster for the amount of text involved.

        • themoonisacheese@sh.itjust.works
          link
          fedilink
          arrow-up
          0
          ·
          1 day ago

          Yeah, I know. Why would anyone ever use them if creating one required a certificate? If the certificate was so cheap as to not be an obstacle then it wouldn’t be a deterrent to malicious replacement of codes either.

          • Caedarai@reddthat.com
            link
            fedilink
            arrow-up
            1
            ·
            8 hours ago

            Because you can make it so that the required certificate/signature has to meet certain criteria to work. For instance, imagine there was a PayPal equivalent type app for paying QR codes, and they required all codes to be signed by one of their business customers (who they have on file). Or with a certificate they themselves issue their customers.