Authenticating the origin of a message does not establish that its contents can be trusted. Even a legitimately authenticated QR code could contain a malicious URL, whether because the issuer is malicious or because their account or system has been compromised.
Cryptographically authenticating QR code issuers could be a useful additional layer of protection, but it does not establish that a destination is safe. Displaying the URL encoded in a QR code before users follow it could help them make more informed decisions, although visible URLs can still be deceptive.
Authentication establishes origin, not trustworthiness.
I wrote a rather long blog post exploring ways to reduce phishing, much of which also applies to QR code phishing (quishing).
One conclusion was that authenticating the origin of a message, whether it is an email, QR code or something else, is not sufficient to establish that its contents can be trusted. Even a legitimately authenticated message can contain a malicious URL, whether because the sender is malicious or because their account or website has been compromised.
That is why I think an important improvement would be to make URLs visible by default, rather than hiding them behind descriptive link text or opening URLs from QR codes without first displaying them. Of course, this does not solve everything: a visible URL can still be deceptive, and recognising a suspicious domain is not always straightforward.
I certainly do not claim to have solved phishing, but I have developed two small tools that might help reduce the risk:
1. A tool that displays the URL contained in each link directly alongside the link text, without requiring users to hover over or click on it. It is available as a browser extension and a Thunderbird add-on. I have also created versions for Gmail and Outlook, but their add-on APIs do not provide a way to modify the displayed email content directly. As a result, an additional click is still required to inspect the links, which rather defeats the purpose of making this information visible without user interaction.
2. A QR code scanning tool that reveals the URL encoded in a QR code before opening it and helps identify potentially suspicious links. It cannot guarantee that a destination is safe, but it can provide additional information before the user decides whether to proceed.
Cryptographically authenticating QR code issuers, as proposed here, seems like an interesting additional layer of protection. However, as noted above, authentication alone does not establish that a destination is safe or that its contents should be trusted.
I would genuinely appreciate feedback on these approaches, their limitations, and whether there are better ways to make link destinations visible without requiring additional user interaction.
Finally, I realise that mentioning my own tools might be considered self promotion. My intention is to contribute to the discussion, make the world slightly safer, and receive constructive feedback. If this comment is inappropriate for Hacker News or this particular discussion, please let me know and I will gladly remove it.
Whenever Anthropic is down, I switch to my other alternative AI provider. If that is also unavailable, or no more tokens left, then I can switch to my local AI. Not the same in terms of quality and speed, but good enough for an experienced engineer to still be more productive than falling back to doing it by hand. For my principal activity I do not want to be dependent on a sole provider. Besides that, I expect that the pending token price increases are going to hurt a lot of people/companies.
Well... tried it on macOS using vanilla gcc, the results surprised me:
$ /bin/cat x.c; gcc -w -o x x.c; ./x
#include <stdio.h>
int main()
{
int a = 5;
a += a++ + a++;
printf("a = %d\n", a);
}
a = 18
Not what I expected.
This must be how it works:
- The first a++ expression results in 5, after a = 6
- The second a++ expression results in 6, after a = 7
- Only then the LHS a is evaluated for the addition-assignment, so we get:
a = 7 + 5 + 6 = 18
Cryptographically authenticating QR code issuers could be a useful additional layer of protection, but it does not establish that a destination is safe. Displaying the URL encoded in a QR code before users follow it could help them make more informed decisions, although visible URLs can still be deceptive.
Authentication establishes origin, not trustworthiness.
reply