3 ms·
Wouldn’t the fix be to encrypt before the api call hits the LLM? You would encrypt/decrypt at a separate layer than the LLM. I am sure i am missing something bu
by infecto 2mo ago
Wouldn’t the fix be to encrypt before the api call hits the LLM? You would encrypt/decrypt at a separate layer than the LLM. I am sure i am missing something but would love to be educated.
- paxys 2mo agoThe LLM needs to read the CoT as part of the conversation. You can ask the models to share them with you. Stronger models will refuse, while weaker ones can be “jailbroken”.
- infecto 2mo agoI don’t think that answers what I am wondering. Asked differently why is encoding/decoding the cot the concern of the LLM?
- paxys 2mo agoIt isn’t the concern of the LLM. Regardless of where the encryption/decryption is happening, the issue is that the LLM needs to access the raw CoT.
- infecto 2mo agoAgain I don’t think you’re really getting at what I am asking. Sorry. My whole point was why does the LLM have access of decrypting. It should happen outside of the LLM layer.
- henryaj 2mo agoI assume it does happen at a different layer, just that that layer is common to all of a provider's models to make conversations portable across models (otherwise the reasoning blocks would all need to be re-encrypted for them work with another model)
- infecto 2mo agoSaid differently I am surprised it is so easily exploited. While there is a nonzero chance to jailbreak, I would think they would have implemented some rigorous methods to try and prevent leakage.