Re: COBOL Compiler for Windows

"Robert" <no@[EMAIL PROTECTED]
> wrote in message 
news:8muk14pvqchs7f765h7ea8uqvsd3rne72b@[EMAIL PROTECTED]
> On Thu, 1 May 2008 10:39:46 +1200, "Pete Dashwood" 
> <dashwood@[EMAIL PROTECTED]
>
> wrote:
>
>>Point 2 is largely an illusion. Certainly, there are no viruses on
>>mainframes, but there will be once they are opened up to the network; it

>>is
>>only a matter of time. (No, I don't have mainframe virus writing on my
>>"TODO" list, but it would be an "interesting" exercise... :-)).
>
> How does a virus get into a database server? You can't send it
executable 
> code.

Wanna bet? You can if you store it as data... :-)

Once it has open ****ts it can be reached in a number of ways, not just
using 
normal protocols...if you can get access to the storage system you're
in...

I was using "virus" loosely, perhaps I should have said "malware"...

What about a stored procedure with a hidden triggerable process? Maybe 
disguised as an existing procedure (Trojan clone) which it replaces in the

system libraries.

What about an entirely new type of virus written specifcally for the 
mainframe architecture? Something that hooks into a particular SVC or
ESTAE 
for example?  Bury a trigger deep in REXX or JCL, cause a data or
addressing 
exception and away you go... :-)

Sure, all fanciful stuff and not very likely. But I'm not really trying
and 
I have no desire to it. Nevertheless, I bet there's someone out there, 
smarter than me who DOES want to do it :-)

And I don't see the mainframes as being ONLY database servers...

Pete.
--
"I used to write COBOL...now I can do anything."