> Now you've confused me. Access to your own spool files is easy. Access > to spool files belonging to others is not. Nor is it possible to access > another virtual machine's memory without its cooperation. In fact, data > is more secure in memory than it is on disk since, once on disk, anyone > with a connection to the disk can see it without restriction. > I contest your statement that "spool access is fairly easy". Not by an > unprivileged user, it isn't.
Commands exist and are shipped with the OS to examine the spool files for other users. No commands are provided to examine pages written by CP for other users. Both can be circumvented if you have access to the disk containing the data, but it's a lot harder. Thus the "fairly easy" -- give your id class B somehow, and you're done. Assembling a virtual machine from pages on disk is a lot harder -- not for ordinary mortals. You're overreading the statement -- relax. It's a matter of comparative degree. ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
