You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
So the bottom line is that we need a separate flag that would tell us that the value is encrypted (or decrypted). Another way would be to check the header, but as pointed out in the discussion, that would not be 100% reliable, as also unencrypted strings can (in theory) start with the same "def5" bytes that would be used to identify the string as encrypted.
I'm interested to have a look at this issue, but unluckily I don't have time for it right now, but if I'll encounter a solution at some point, I will definitively post more about it here or make a pull request.
Currently, we decrypt if the string is long. This is not the right way to do it, we should check if the header is set.
The text was updated successfully, but these errors were encountered: