Hello from Gregg C Levine All of this discussion regarding viruses and S/390 Linux and VM, brings up another question. And here it is: When the worm written by RTM, Bob Morris son, ravaged the Internet, about 14 years ago, did it hit any connected VM systems that the people here are aware of? And can remember? I remember the accounts behind it, and I have here a book, written by Cliff Stoll which contains his accounts, in the last few chapters, of his regular story. It was very destructive to the different flavors of Unix running out there. But since as he comments, the Internet isn't entirely all Unix, (Pick a name!), it does contain systems which are running IBM operating systems. So they shouldn't have been effected. ------------------- Gregg C Levine [EMAIL PROTECTED] ------------------------------------------------------------ "The Force will be with you...Always." Obi-Wan Kenobi "Use the Force, Luke."� Obi-Wan Kenobi (This company dedicates this E-Mail to General Obi-Wan Kenobi ) (This company dedicates this E-Mail to Master Yoda )
> -----Original Message----- > From: Linux on 390 Port [mailto:[EMAIL PROTECTED]] On Behalf Of > John Alvord > Sent: Thursday, February 06, 2003 11:41 AM > To: [EMAIL PROTECTED] > Subject: Re: [LINUX-390] Newbie Virus question > > On Wed, 5 Feb 2003, Coffin Michael C wrote: > > > Agreed. In order for a virus to have any effect on VM it would have > > to be written in such a way as to launch itself and run in CMS in a > > user virtual machine (extremely unlikely) and/or infect CP itself > > (next to impossible, if not completely impossible - certainly > > impossible from a non-priviledged virtual machine which your > > Linux/390's should be). > > > > So the long and short of it is that even if you were to receive a virus on > > Linux/390, you are 99.999999999% sure it cannot effect VM in any way, with > > exceptions noted. > > > That is also true for unix... until you get into root... for VM it would > be to get logged on to the privileged user(s) who can write new kernels, > save new shared systems, etc etc. For MVS it would be to run a program > authorized. There is always a way... > > John Alvord
