Re: And thus..
How do you know which process REALLY said what if all you have to work with is ASCII, which the pwned process is fully capable of using as well, meaning there's no way to distinguish a well-disguised fake log output pretending to be another process from the actual process. The range of your output is too limited to properly distinguish between them. Anything you can try to use within the ASCII range to safeguard them, the rogue process can mimic. It's a rogue edge case, just like you have no way to say a coin flip landed edge (the LITERAL edge case) if all you have to work with is 0 (heads) and 1 (tails). See where I'm going with this? Properly safeguarding the log from rogue output requires something beyond ASCII. It's a necessary complexity.