4 ms·
I tried it with "dssdf4t5456456456456$"" which is just random hitting keys on my keyboard, and it printed "you should see an output like this:" and it followed
by coldtea 4y ago
I tried it with "dssdf4t5456456456456$"" which is just random hitting keys on my keyboard, and it printed "you should see an output like this:" and it followed with an encrypted value.
It didn't however decrypt to the original value on jwt.io.
But looking more closely, I saw that it DID in fact match the original value, but without the last "$", as if it had encrypted only the "dssdf4t5456456456456" part.
Tried again with: "letsseeifthiswillworkHN"
and it gave me:
"eyJhbGciOiAiSFMyNTYiLCAidHlwIjogIkpXVCJ9.eyJpbnB1dCI6ICJsZXRzc2VlaWZ0aGlzd2lsbHdvcmtITiJ9.1dYfq9V8WJ4g4vV7Pd-J_YeVVJ2WZLjSbVt-gA9z1mQ"
as the expected output, for which jwt.io gives:
{
"input": "letsseeifthiswillworkHN"
}
[Edit] Apparently the payload part as another mentioned is base64. So GPT knew to separate the payload part and to do base64 encoding.
I guess the base64 encoding part is quite trivial, and something even a simple NN can learn, as it's very simple substitution rules, basically a lookup table is enough...
- travisjungroth 4y agoIm surprised this worked. I was just trying to get it to translate Morse code and it was doing terribly. My guess was because of the tokenization being multiple letters.