I've been researching web app -> mainframe security from a software
engineering perspective for about the last six months. If anyone from
a mainframe background wants to collaborate, I'd be more than happy to
share as I have a few challenges:
a) I'm working from secondary resources (web pag
Searching through
http://www.csl.sri.com/neumann/illustrative.html
gives these COBOL-related RISKS items. The initial
character descriptors are defined there. In the citations,
* R relates to RISKS (archives at risks.org)
* S relates to SIGSOFT Software Engineering Notes (archives at
www
At 12:13 AM -0400 11/2/07, Mark Rockman wrote:
> The adolescent minds that engage in "exploits" wouldn't know COBOL if a
>printout fell out a window and onto their heads. I'm sure you can write
>COBOL programs that crash, but it must be hard to make them take control
>of the operating system.
Of
On Nov 2, 2007, at 12:13 AM, Mark Rockman wrote:
I'm sure you can write COBOL programs that crash, but it must be
hard to make them take control of the operating system.
If software exploits were "only" isolated to OS compromise, that'd be
just fine. But let's not forget that an application
| The adolescent minds that engage in "exploits" wouldn't know COBOL if
| a printout fell out a window and onto their heads.
I would have thought we were beyond this kind of ignorance by now.
Sure, there are still script kiddies out there. But these days the
attackers are sophisticated, educate
Hi Mark,
: The adolescent minds that engage in "exploits" wouldn't know COBOL if a
: printout fell out a window and onto their heads. I'm sure you can write
: COBOL programs that crash, but it must be hard to make them take control
: of the operating system. COBOL programs are heavy into uni