This is fun. Google Gemini’s “Summarize email” function is vulnerable to invisible prompt injection utilized to deceive users, including with fake security alerts.
This is fun. Google Gemini’s “Summarize email” function is vulnerable to invisible prompt injection utilized to deceive users, including with fake security alerts.
SANITIZE YOUR INPUTS.
Everyone rushing to LLM-ify everything forgot every lesson about input sanitization.
smdh.
@neurovagrant I'm pretty sure "sanitizing" inputs is fundamentally impossible, as in you must solve the Halting Problem in order to accomplish it.
If you don't want hostile inputs, you need to implement much more aggressive models of what input can even be, and you need to enforce those. Cf. the entire field of language-theoretic security https://langsec.org/ . tl;dr: "be liberal in what you accept" is a plan that has been extensively tested and comprehensively debunked.
@davidfetter @neurovagrant The halting problem is decidable for any finite computer. Just limit how much RAM and compute time can be used.
Beyond that, though, why is the model taking instructions from an email at all?
@bob_zim this is pretty much equivalent to the argument made by the langsec folks. I get the impulse to have an argument. I have it myself on occasion, as @neurovagrant can doubtless attest.
Maybe we should instead engage with the question of validating rather than sanitizing, that former perforce rejecting a lot of inputs that attempts to sanitize would accept. This rapidly runs into thought-terminating clichés like "the customer is always right," and that in turn leads directly into the political economy of software development, a generative discussion.
NOP
over some SUBQ
to avoid decrementing lives in games 🤣)@neurovagrant And of course, "sanitize your inputs" is going to fall on deaf ears among the public at large. Hell, you can't even get most people to wash their hands after using the restroom, it seems.
Seriously though, if the system depends on users taking specific actions to ensure their safety, the system is flawed in my opinion. Basically, "whenever you blame the users as a group, you're on the wrong side of the issue" has long been my philosophy.
Interfaces should be designed to be easy to use safely and difficult to use un-safely.
@neurovagrant Yeah, I meant the blog post itself. Very hard to read.
As for Gmail, the only native way I know to see the actual text is through Show Original, which of course is a mess for HTML.
However ... my primary MUA for non-Gmail is mutt, which renders only plain text, and I am pretty good at scanning through html visually when a plain text part hasn't been included. I do this mainly as a pretty damned close to 100% way to avoid malware and triggering beacons, since the HTML is never rendered. (If there's some message where I really need to render the HTML, I send it off to an essentially sandboxed system).
@lauren Respect.
It took me a while, when I was in IT, to understand my users that rolled like this. Especially the ones that stuck to terminal-only email clients.
@lauren @neurovagrant Safari has a “reader” view which strips away most styling. Gives a consistent font, consistent line length, and so on. It renders black-on-white in light mode. I haven’t checked other browsers in a while, but I’m under the impression at least Chrome and Firefox have something similar.
Incidentally, I have some pretty gnarly astigmatic distortion in one of my eyes from repeated corneal tearing (currently double astigmatism, for a total of three images, but the number, angle, and relative displacement change). I don’t personally find the gray-on-black of the original article harder to read. Not doubting your experience, but there may be more going on.
@neurovagrant Isn't that AWESOME!?!!?
Input validation, people. It's not just for breakfast anymore.
@neurovagrant The presence of bugs like this would make it extremely irresponsible to enable Gemini by default, unrequested by the user.
So surely they wouldn't... *checks recent news*. Oh.