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.
The 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”.
I don’t think that answers what I am wondering. Asked differently why is encoding/decoding the cot the concern of the LLM?
It 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.
Again 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.
Wild this would get downvoted. I am asking a question, the bots must have come in.
LLM does not work on encrypted tokens. It happens at the API gateway.
I 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)
Said 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.