Subj : Re: Mystic and DosEmu, am I missing something obvious?
To   : All
From : Underminer
Date : Mon May 10 2021 07:42 am

> 
> I suspect the argument passing and path issues. Is this SBBS or Mystic? I see 
> it's Windows, but which version or is that just due to the DOS emulation?
> Mystic doesn't allow things outside it's path, generally meaning it has to be
> under /mystic. So if the drive is really e:\mystic to DOS that's OK, but 
> if it's c:\mystic and the door is e:\anything it's not likely to work. Mystic
> changes from root owner to whatever whatever owns the mystic directory and 
> won't let things outside the mystic path do much if anything. The DD command 
> (Linux door) is an exception to that, you can run games from /usr/local/games 
> using DD. Generally the temps have to be under mystic and that causes doors
> not to work outside of the mystic directory. No idea if SBBS does that, but 
> I wouldn't expect it. I think more people work on that and it's inherited 
> the older DOS paths so they aren't  as secure as the way g00r00 does it.
> 
There's no black magic going on with Mystic, at least not in *nix. Whether you can access things outside of /mystic or not, or whether they can access /mystic is entirely down to your permissions and ownership. I have a few instances on a few different LXC containers to test different things out, and in all cases have a shared bind mount with tools. There may or may not be additional checks being run within the windows binaries, but I wouldn't know as I don't touch anything MS if I can help it.
--- SBBSecho 3.14-Linux
 * Origin: The Undermine - bbs.undermine.ca (21:4/103)

.