Fill Access does not seem to be working.

Please post your problem description here

Moderator: Barb@Invincea

Post Reply
shadowen
Posts: 1
Joined: Fri Aug 31, 2012 5:07 pm

Fill Access does not seem to be working.

Post by shadowen » Fri Aug 31, 2012 5:17 pm

Version 3.74 (64bit).

The full access does not seem to be working..

I use firefox - sandboxed, and downloadthemall plugin, which I use when downloading icon sets- much faster than 32 rightclicks.

However, when I try to create a directory, it creates the "new directory" but I cannot rename it as it always says - in use by another program.

So I try to directly create a folder, that appears to work, however, I cannot write anything in the folder, though it does appear to be written to the "real" directory. All files endup with file access errors, and are not written to the "real disk" nor the sandboxed environment.

Downloading a file directly and storing it, ends up in the sandboxed environment...

I have a network drive, I use to download stuff to - nothing is ever run from there, so it's quite safe..

so I have given all sandboxed programs (in the default sandbox) full access to drive y:\ which is my network drive, but trying to create a directory is not doable.

and writing a single file to y:\icons\setA will end up in the sandboxed environment, but writing a directory, and many files just fail.

How do I allow full access to a drive, it does not seem to work via the sandboxie settings/resource access menu, using full or direct access..

Guest10
Posts: 5134
Joined: Sun Apr 27, 2008 5:24 pm
Location: Ohio, USA

Post by Guest10 » Fri Aug 31, 2012 5:53 pm

It sounds like a problem that has existed for a long time.
I have a network attached storage drive (Z: ) and cannot write directly to it from sandboxed programs.

The only way I can store files on that NAS drive is to create a TrueCrypt volume on the drive; mount that volume as drive letter (K: ); and then I can write to K: and the files wind up being stored in the TrueCrypt volume on Z:.
Paul
Win 10 Home 64-bit (w/admin rights) - Zone Alarm Pro Firewall, MalwareBytes Premium A/V, Firefox, Thunderbird
Sandboxie user since March 2007

tzuk
Sandboxie Founder
Sandboxie Founder
Posts: 16076
Joined: Tue Jun 22, 2004 12:57 pm

Post by tzuk » Sat Sep 01, 2012 12:58 pm

Guest10 do you remember if adding \Device\Mup or \Device\LanmanRedirector as a full/direct access path fixed the problem?
(Of course with the effect that all network access would not be sandboxed, and not only a specific network drive.)
tzuk

Guest10
Posts: 5134
Joined: Sun Apr 27, 2008 5:24 pm
Location: Ohio, USA

Post by Guest10 » Sat Sep 01, 2012 3:21 pm

Well, I have to admit that the situation is not as I remember it. It seems like it's better than it was.

With a simple Direct Access setting:
OpenFilePath=Z:\
I can save files to Z:, and I can create "New Folder", but I can't name the new folder.
"Cannot rename New Folder. Access is denied."

If I create folders while unsandboxed, I have no trouble saving files in any folder or sub-folder on Z: drive, when I use sandboxed Notepad or Wordpad with the above Direct Access setting.

Limiting the access to notepad.exe -
OpenFilePath=notepad.exe,Z:\
With this setting:
Notepad can save files to any existing folder.
Wordpad cannot access Z: drive at all from a Browse box, even to read the root directory, unless a
ReadFilePath=Z:\
setting is used.
That's the setting that I have been using in [GlobalSettings] just to allow for the possibility of making reads, without generating error messages.
That setting was removed for these tests.

So you still need some setting just to allow sandboxed programs to read from the drive, even it's only a ReadFilePath setting.

Each of the following settings gives the same result as "OpenFilePath=Z:\" :

OpenPipePath=Z:\

OpenFilePath=\Device\Mup

OpenPipePath=\Device\Mup

OpenPipePath=\Device\Mup*

OpenFilePath=\Device\LanmanRedirector

OpenFilePath=\Device\LanmanRedirector*

OpenPipePath=\Device\LanmanRedirector

OpenPipePath=\Device\LanmanRedirector*

OpenPipePath=\Device\LanmanRedirector*
OpenPipePath=\Device\Mup*

OpenPipePath=\Device\LanmanRedirector*
OpenPipePath=\Device\Mup*
OpenFilePath=Z:\

OpenPipePath=\Device\LanmanRedirector*
OpenPipePath=\Device\Mup*
OpenPipePath=Z:\

We have tried different LanmanRedirector settings in the past, based on the output from the Resource Access Monitor for my drive:
(Drive) \Device\LanmanRedirector\;Z:0000000000012ecb\MSS-017E9F\****
Paul
Win 10 Home 64-bit (w/admin rights) - Zone Alarm Pro Firewall, MalwareBytes Premium A/V, Firefox, Thunderbird
Sandboxie user since March 2007

tzuk
Sandboxie Founder
Sandboxie Founder
Posts: 16076
Joined: Tue Jun 22, 2004 12:57 pm

Post by tzuk » Sun Sep 02, 2012 4:43 pm

Thanks for checking. I see this is still a bit problematic, but I'm not sure what I can do about it at this point. I think we'll have to leave it at that for now.
tzuk

flip_lmb
Posts: 15
Joined: Fri Mar 16, 2012 9:28 am

Post by flip_lmb » Wed Dec 12, 2012 10:26 am

Hi tzuk, I was wondering if you've got any news regarding this issue? I have an app which I run within a sandbox (which is cleared on exit), that creates a csv file on a network share. I've tried all the OpenFilePath/OpenPipePath settings, but the file always gets deleted.

Phil

Post Reply

Who is online

Users browsing this forum: No registered users and 19 guests