Subj : Family executables again
To   : David Noon
From : Mike Luther
Date : Mon Oct 15 2001 01:21 am

OK Dave ..


DN> Under OS/2, Win32s programs need to be run in a WIN-OS/2 session. This
DN> means that a Win16 shell [typically PROGMAN.EXE or
DN> WINFILE.EXE] must already be running, or a WPS
DN> "program reference object"  must be created to
DN> initiate WIN-OS/2. Neither of these is performed by
DN> Nimda, because it isn't coded for OS/2. [Yes, I know
DN> 4OS2 can start Win16 programs automatically, but
DN> Win32s programs are linked as PE, not NE, load
DN> modules.]

I've now made thta mental connection.  I use almost no WIN programs at all,thus
don't thing about all this until prompted... (!)

DN> The only way you'll get a Nimda infection on an OS/2
DN> machine is if you have an infected Win32 machine
DN> owning filesystem shares with write permissions to
DN> your OS/2 box.

Oh that's true enough.  But family executables could be written between WIN and
OS/2 if one worked hard enough at it.  Coding Raiders of the Lost Vark would be
a larger job, sure.  But coding a small bit of code as family wouldn't be quite
so much of a pigglet, one would think.  Look at AEDIT, for example.


--> Sleep well; OS/2's still awake! ;)

Mike @ 1:117/3001



--- Maximus/2 3.01
* Origin: Ziplog Public Port (1:117/3001)

You are viewing proxied material from cvs.synchro.net. The copyright of proxied material belongs to its original authors. Any comments or complaints in relation to proxied material should be directed to the original authors of the content concerned. Please see the disclaimer for more details.