Arnaud Nicolet wrote:
Le 29 déc. 08 à 19:33 (soir), Bart Silverstrim a écrit:
I was pointing out one reason why it wouldn't happen. With most VM
systems you have it sandboxed to a degree...there's no reason to
expose the Applications folder to a Windows VM on the Mac. Those files
are useless to the virtual machine guest.
Well, there's an option to just share the entire startup disk. Many
users may share it to avoid asking themselves what to share in case of
multiple folders needed to be shared (sometimes humans prefer the easier
way, sadly).
Haven't used Parallels, but I'd believe it. Have used VMWare, Virtalbox,
and a few others. They didn't share an entire startup disk...silly option.
If he shared and/or exposed the entire filesystem to the Windows
guest, then in my opinion it's asking for problems. But the malware
still would be scratching its' head at most of the filesystem
peculiarities it would encounter with a shared drive, it would be
limited to infecting just what it knows how to infect via (probably)
cifs, the file sharing protocol. The raw filesystem would not work
with the guest.
Hmm... I think the share is "converted" in FAT32 (otherwise, the guest
OS wouldn't be allowed to write).
Again, haven't used it, but doubt that...if it is, it's lying to the VM.
Fat32 isn't anything like HFS...
The implementations I have seen normally used CIFS (windows sharing
protocol) which does allow read and write permissions.
_______________________________________________
Unsubscribe or switch delivery mode:
<http://www.realsoftware.com/support/listmanager/>
Search the archives:
<http://support.realsoftware.com/listarchives/lists.html>
|