(Sandboxie (5.33.6), an old, ancient version. Nonetheless.)
2 (video files)
Code: Select all
1 NOT in sandbox [N-vid]
1 in a sandbox (Sandboxie) [S-vid]
(Everything running normally, outside of the sandbox)
highlight N (then)
click+highlight S
(now both are highlighted, first N, then S)
Hit <CR>
both open (in separate MPUI windows)
both, are running in a sandbox - even though N is Not in a sandbox
highlight S (then)
click+highlight N
(now both are highlighted, first S, then N)
Hit <CR>
both open (in separate MPUI windows)
both, are running NOT in a sandboxed - even though S is in a sandbox
"in a sandbox"
- the file physically exists in a directory (tree) that is defined (to &) as a Sandboxie sandbox
(not that i care, in this case, but) now... is that cause of Everything... maybe spawning
synchronous exec()'s & since the last selected file (& depending on where the last selected
file exists) was or was not in the sandbox, subsequent exec() (for any further files) follow
in suit... ? or... would similar happen elsewhere ? or... might mplayer be playing in...
or Sandboxie itself, or... ?
(not atypical for me to have any particular file or files open in a sandbox, & so that it was or was not,
might not have meant anything to me, to be of concern or different, but in this particular case
i certainly knew that 1 of the 2 was not in any sandbox, so when i saw that both files came up
sandboxed, that certainly drew my attention)
now... how else to test?
what else, from within 1 program, can show both S & N, & can also open them "simultaneously" ?
appears... SendTo <program> opens outside the sandbox, always?
Open With <program> opens outside the sandbox, always?
Windows Explorer, opened to a sandboxed directory, opens the file, sandboxed
from within sandbox
> start team128.mp4 & c:\out\team128.mp4
or
> start c:\out\team128.mp4 & team128.mp4
opens both .mp4, sandboxed
i guess that's expected, as the start is running sandboxed, so anything started from the start
should also run sandboxed
(similarly if something was started from within the sandbox, opened outside the sandbox,
that would defeat the entire purpose of the sandbox)
from outside of sandbox
> C:\out>start team128.mp4 & C:\Local\SANDBOX\MPV\drive\C\Team128.mp4
or
> C:\out>start C:\Local\SANDBOX\MPV\drive\C\Team128.mp4 & team128.mp4
opens both .mp4, NOT sandboxed
i guess that's expected, as the start is NOT running sandboxed, so you would not expect ?
a file /pointed to/ that only happens to exist within the sandbox to open sandboxed?
(above is the same with or without the start, entirely, with or without, cmd /c,
[only diff with cmd is that the files fire synchronously])
now, the fact that Windows Explorer, double-click on a file that exists within a sandbox,
means... just what? that the double-click, the exec() is being run in the context of the
sandbox? or... does sandboxie "hook" into Windows Explorer, so in that respect W/E
"knows" that the sandboxed directory is a sandbox, so says, "OK then, lets open you
in that sandbox", or... ?
(context-menu) Edit with VIM, does NOT open a file in a sandbox, sandboxed
(i thought i had a note as to where in the registry that was located... ?)
(back in 2016, i posted something about Edit with VIM @voidtools...)
so... where am i ? not sure ?
(& i'll note)
IF 1 sandbox, S, 1 not, N
AND *also* IF diff volumes, then they WILL open as 1 sandbox, 1 not