Hi,Sounds like one for Tech Support.If you can dump the page to get the row contents and have the key perhaps Tech Support can provide a small C program to decrypt it.
A small C program is what I was hoping for, but so far they haven't offered that. My guess – and it's only that – is that the encrypted data contains an odd character (perhaps an emoji or something) that's throwing off the algorithm.
I'm not sure how that would help. The data in the "bad" column is 43 bytes wide and the column allows a length of up to 250.
Won't that mess up a checksum?
As soon as you truncate even one character off the end of the string, the error [correctly and expectedly] pivots to -26012, "The internal base64 decoding function failed."
Now we're getting somewhere! When I set EILSEQ_COMPAT_MODE to 1, the error changes from 202 to this: 23103: Code-set conversion function failed due to illegal sequence or invalid value.
If it's illegal in en_US.utf8, what codeset might it be legal in?
Andreas is our winner and gets a cookie! The database in question is a UTF-8 database. I unloaded the data and loaded it into a Latin-1 database and was able to decrypt! There is indeed an offending character: the Spanish Flag emoji, which the user entered after his name.
Now the problem pivots: Shouldn't the engine have thrown an error on the encryption step?