The validation code for paths, intents, etc. is currently located in the standard library. This makes it easy to test, but it's the wrong place to enforce! Move the validation module into the kernel, and hook it up to the is_valid functions in the system call handlers, so that the kernel will reject the creation of invalid identifiers.
dthain
commented
5 years ago
The validation code for paths, intents, etc. is currently located in the standard library. This makes it easy to test, but it's the wrong place to enforce! Move the validation module into the kernel, and hook it up to the
is_validfunctions in the system call handlers, so that the kernel will reject the creation of invalid identifiers.