https://news.ycombinator.com/item?id=35929145
I haven't heard an argument why this wouldn't work.
101–110 of 183 posts
https://news.ycombinator.com/item?id=35929145
I haven't heard an argument why this wouldn't work.
I understand doing this from a red-team perspective, but what is the point in actual usage? I see GPT as a tool to make "my life easier", help me with tedious stuff, maybe point out some dark corners etc Why would I go and try to break my hammer when I need it to actually put the nails in? Will there be users doing that? Sure! Will I be doing that? Not really, I have real issues to take care of and GPT helps do that.…
Here's why I think this is a big problem for a lot of the things people want to build with LLMs: https://simonwillison.net/2023/Apr/14/worst-that-can-happen/ I suggest reading my blog closer if you think I'm trying to scare people off GPT. Take a look at these series of posts for example: https://simonwillison.net/series/using-chatgpt/ - about constructive ways to use ChatGPT https://simonwillison.net/series/llms-on-…
With all due respect, I would also like to market someone else who has also been posting similar content, but for some reason those posts never make it to the top. If you don't believe me, you can check the following submissions:
[0]: https://news.ycombinator.com/item?id=35745457
[1]: https://news.ycombinator.com/item?id=35915140
They have been consistently putting the risks of LLMs. Thanks for spreading the information though. Cheers.
In that sense I agree it could be a problem solved without "ai". Simon's approach does use another language model, maybe we need to build more way of logically sandboxing code or just better fine grained access control
Can’t you just ask another LLM to analyse the text of the input to determine if it’s an attempted prompt injection?
I still claim prompt injection is solvable with special tokens and fine-tuning: https://news.ycombinator.com/item?id=35929145 I haven't heard an argument why this wouldn't work.
1. Given the availability of both LLAMA and training techniques like LORA, we're well past the stage where people should be able to get away with "prove this wouldn't work" arguments. Anyone with a hundred dollars or so to spare could fine-tune LLAMA using the methods you're talking about and prove that this technique does work. But nobody across the entire Internet has provided that proof. In other words, talk is cheap.
2. From a functionality perspective, separating context isn't a perfect solution because LLMs are called to process text within user context, so it's not as simple as just saying "don't process anything between these lines." You generally do want to process the stuff between those lines and that opens you up to vulnerabilities. Let's say you can separate system prompts and user prompts. You're still vulnerable to data poisoning, you're still vulnerable to redefining words, etc...
3. People sometimes compare LLMs to humans. I don't like the comparison, but lets roll with it for a second. If your point of view is that these things can exhibit human-level performance, then you have to ask: given that humans themselves can't be trained to fully avoid phishing attacks and malicious instructions, what's special about an LLM that would make it more capable than a human being at separating context?
4. But there's a growing body of evidence that RHLF training can not result in 100% guarantees about output at all. We don't really have any examples of RHLF training that's resulted in a behavior that the LLM can't be broken out of. So why assume that this specific RHLF technique would have different performance than all of the other RHLF tuning we've done?
In your linked comment, you say:
> Perhaps there are some fancy exploits which would still bamboozle the model, but those could be ironed out over time with improved fine-tuning, similar to how OpenAI managed to make ChatGPT-4 mostly resistant to "jailbreaks".
But GPT-4 is not mostly resistant to jailbreaking. It's still pretty vulnerable. We don't have any evidence that RHLF tuning is good enough to actually restrict a model for security purposes.
5. Finally, let's say that you're right. That would be a very good thing. But it wouldn't change anything about the present. Even if you're right and you can tune a model to avoid prompt injection, none of the current models people are building on top of are tuned in that way. So they're still vulnerable and this is still a pretty big deal. We're still in a world where none of the current models have defenses against this, and yet we're building applications on top of them that are dangerous.
So I don't think people pointing out that problem are over-exaggerating. All of the current models are vulnerable.
----
But ultimately, I go back to #1. Everyone on the Internet has access to LLAMA now. We're no longer in a world where only OpenAI can try things. Is it weird to you that nobody has plunked down a couple hundred dollars and demonstrated a working example of the defense you propose?
Earlier quoted context omitted.
And then gdpr fucks that up that nice clean concept completely
GDPR only affects data you shouldn't have or keep in the first place.
https://gdpr-info.eu/art-17-gdpr/
Implementing this as a rollback-able delete will not be compliant.
It feels like this vulnerability reflects how LLMs are indeed a huge step not just towards machine intelligence but also towards AI which behaves similarly to people. After all, isn't prompt manipulation pretty similar to social engineering or a similar human-to-human exploit?