Hi,
I've just bought Sandboxie, great piece of software at a reasonable price. Keep up the good work!
Basically I'm creating a single sandbox that will run all my browsers as 'forced programs', one of which is the natively installed IE10 in Windows 8. This works fine on the desktop view in Windows 8, all highlighted nicely to let idiots like me know that Sandboxie is doing it's thing.
My question is, since this 'forcing' operates off the program exe, is it also forcing the 'metro' version of IE10?
I'm assuming that the 'Metro' version of IE10 is the same exe, just with a different GUI, but I decided that I'm not actually sure of that. Do I need to add the Metro version separately?
Similarly, is this true of all 'Metro' apps, namely that they are different programs even if they have a desktop 'cousin'?
Cheers
Sandbox IE10 (Internet Explorer 10) Sandboxie - Metro/Modern
So this goes some way to answering the above questions.
All Metro apps, are indeed different programs and can be found as per below:
http://www.thewindowsclub.com/windows-8 ... r-location
I'll give it a whirl and see what starts to smoke....
All Metro apps, are indeed different programs and can be found as per below:
http://www.thewindowsclub.com/windows-8 ... r-location
I'm guessing this means therefore that they must be dealt with just like any other application, i.e. explicitly added as a program or as part of a program group if they are to be forced programs in Sandboxie.The ‘Metro’ Applications in Windows 8 are installed in the WindowsApps folder located in the C:\Program Files folder. It is a Hidden folder, so in order to see it, you will have to first open Folder Options and check the Show hidden files, folders and drives option.
I'll give it a whirl and see what starts to smoke....
So the first obstacle to that method is that only the system has full control. Administrators are only given Read and Execute Access, which under standard Windows 8 installation account won't let you in to the folder.
Two ways off the top of my head to get around this:
1. Enable the true administrator account and get in there and beat things around till they get the hint.
2. Use the now enabled real admin account to change the permissions so that 'wimpy standard' administrator accounts have full access, and then go back and beat things about till they get the hint.
3. Use the 'take ownership' registry tweak and see if it allows you in after that.
One or all of these might have serious security implications, or might not. I don't know enough about and I'm too tired to look into it now.
I'll let you know what I come up with in future (unless someone has already cracked this one for me.....hint, hint )
Two ways off the top of my head to get around this:
1. Enable the true administrator account and get in there and beat things around till they get the hint.
2. Use the now enabled real admin account to change the permissions so that 'wimpy standard' administrator accounts have full access, and then go back and beat things about till they get the hint.
3. Use the 'take ownership' registry tweak and see if it allows you in after that.
One or all of these might have serious security implications, or might not. I don't know enough about and I'm too tired to look into it now.
I'll let you know what I come up with in future (unless someone has already cracked this one for me.....hint, hint )
Who is online
Users browsing this forum: No registered users and 1 guest