https://en.wikipedia.org/wiki/Private_Use_Areas
I came across a Python library that passed the ASCII range into one of these non printable character ranges and then into a database. If someone was doing that manually with a hex table, how is that detected and mitigated?
Whatever you’re trying to achieve: You’re decidedly approaching it from the wrong angle.
I can’t work out what you’re asking.
You use “mitigated” like this is some kind of exploit but it’s just unicode text still.
What is the problem with private use areas of unicode?
It is non printing. It cannot be seen or scanned or highlighted. It looks like nothing, except the file size is large with more hex than should be in the binary.
I’m still not seeing why that is a problem. The information remains even if it has no glyphs.
It does not. It can be rendered as a control character.
But… so what?
No one reads hex as strings IRL.
But it means nothing. You can cypher in much more efficient or clever ways.
Unrelated to the question or circumstance
