Re: Fix Security (was: Paging file)

So, what you are saying is that any third-party vendor with a bloated sense
of self importance could decide he needs a trifle more authority to make his
software as effective as he'd like it to be, so he could quietly just take
what ever he wants and no one would be the wiser?

It isn't malware thats the serious problem, its egoware.  These 3rd-party
vendors have the know-how and resources to do just what you have laid out.
If I've read you right this could become our own version of "DLL Hell"?

Suddenly I feel this real cold draft blowing down my shirt collar.



---------------------------------------------------------
Booth Martin   http://www.MartinVT.com
Booth@MartinVT.com
---------------------------------------------------------

-------Original Message-------

From: midrange-l@midrange.com
Date: Wednesday, October 30, 2002 08:52:46 AM
To: midrange-l@midrange.com
Subject: Re: Fix Security (was: Paging file)



You guys just won't see it. On AS/400 number one (yours)
you have all the authority you need. You make a program
(normal user state, no adoption of authority) and patch it
to make it malware. Then recalculate the program validation
value and save the program. Transfer the save file to
another AS/400 (the one you are attacking) and restore
the malware program. For this you need only enough
authority to restore the program. You might charm the
system operator or the user to restore it for you. Maybe
it is a demo program that also does something useful
and interesting. Once the program is restored (as it
will with no problems as it is just a user state program;
you can even sign it for that matter) you run it and now
you are God on the other AS/400.