http://www.csicop.org/si/show/thinking_ ... trade-offs
The tipping point was when it became so easy to restore a machine to a previous clean state with the advent of virtual machines. This allows you to freeze the exact state of a machine, do something that may risk infection of your computer, and revert back to that clean state afterwards and know that your machine is not infected.
That sounds easy and good and I remember that people here use pupsave that way to restore the known pupsave and delete the one that may have got corrupted.
But that only works for malware that end up in pupsave not those that download itself outside of pupsave.
One would have to set the HDD as read only and then open it each time one want to save something on it.
But back to the virtuality.
Suppose I start up Fluppy and then start vbox and in that vbox start up a Vbox version of Fluppy.
Would that create a "Sandboxed" version of Fluppy that can not reach the HDD?
How am I supposed to save a picture of the screen or some news medua text or something.
Sure I could send it as mail to Gmail or something and use that as a Cloud computing storage. ?
Could someone explain what is the pro et cons?
Are there a vbox pet in PPM for Fluppy? Or some pet on puppy wiki or somewhere?
Would not the bad guy go directly on to the booted Flupy and not care for the virtual one?
I would still make hdd untouchable by chainging the write eprsimssion in a way they can not change.
But how can I change it to writable then without them being able to do the same.
I would have to take it out or cut power to it and work only on USB memory stick that one can set mechanically to not be writeable.