|26 Sep 2011||#1|
| || |
Keeping Guest Infections from Host via SUBST & ICACLS on Shares
I have many uses for a VM, including the taking of risks I avoid on the Host.
I am looking at both VMWare 3.1.4 build-385536 and VirtualBox 4.1.2.r73507
Is there any difference in security risks and capability between the use of a conventional shared folder at
where X:\ is the result of the CMD.EXE command
SUBST X: G:\2_Way\
I prefer to avoid depending on my memory, therefore it will be easier to take no action UNLESS I require 2 way access, in which case a desktop shortcut will run the SUBST command to give access via X:\
How can I mitigate the risk if something bad gets in G:\2_Way\ ?
Should I use ICACLS or similar on the 2_WAY folder to prohibit execution ?
I did a few simple things by trial and error with CACLS under XP.
I am new to Windows 7 and ICACLS seems to have more bells and whistles.
I would appreciate being given the CMD.EXE command string for the Host to restrict the contents of
Should I similarly supplement host protection if the Guest is given Read Access to
There was a time when I thought files were either write protected or not,
but now there are so many flavours of protection I am bewildered.
e.g. ICACLS lists under "perm"
RX - read and execute access
R - read-only access
and does "R" mean that malware can be read and copied but not executed ?
|My System Specs|
|Similar help and support threads for2: Keeping Guest Infections from Host via SUBST & ICACLS on Shares|
|Can one get VBA help on host when Access on XP mode guest?||Virtualization|
|VirtualBox Shared folder-Win 7 Host & Win XP Guest||Virtualization|
|Clipboard not working between host and p2v guest||Virtualization|
|64 bit Host 32 bit guest - How to do?||Virtualization|
|VM with guest XP and Host Win7 not connect to internet||Virtualization|
|What's Best Practice for Getting Rid of Guest Host OS?||Virtualization|
|Accessing Host applications from Guest in VirtualBox||Software|