Storage -> New Domain -> Data / POSIX -> any characters can be entered into Path / VFS Type / Mount Options for a POSIX domain, including spaces, non-ASCII chars, etc. All these should be blocked.
if we block anything, should be done at engine level. though not sure if we want to block things here. ayal?
If it's CIFS it might contain non-ascii chars and spaces, so blocking is not the solution. I cannot guarantee that trying to mount such a thing would actually work though (as I'm not sure we handle this properly in the entire stack). Closing as notabug. Feel free to reopen if mount fails when path contains a nonascii char and trying to pass it fails.