4 ms·
The actual attack is described near the end of the article—ChatGPT and friends send tokens as fast as they are generated, and the encrypted data doesn't mask th
by lolinder 3y ago
The actual attack is described near the end of the article—ChatGPT and friends send tokens as fast as they are generated, and the encrypted data doesn't mask the size of the token. This allows the attacker to guess the size of each token as it comes in, which they feed into a specialized model that guesses the word sequence based on the token lengths.
Mitigating this should be very simple—pad the token with null to some reasonable length before sending it, then clip it on the client side. This would result in slightly higher bandwidth usage, but not enough to be perceptible.
- williamcotton 3y agoThere’s something very enticing to a cracker to have the same data passed back each time as well, that conversation history with the chat bot.
- hedora 3y agoSSH already has mitigations for this, for what it's worth.