Validate Path considers all control characters and ':' as invalid

[bollhals]

The ValidatePath function

• validates that none of the chars is a control character
• then forwards to ValidatePathImpl, which
  • validates that no ':' exists.

AFAIK the only not allowed char in a linux filesystem is a '\0' char. Windows has a few more.

Therefore I'm wondering whether the validation could change to either:

• Only validate the common set => no '\0' exists
  OR
• Allow FS to define their own set of illegal chars to validate via the ctor

[xoofx]

Maybe related to this old issue #70