RE: Buffer overflow and code execution on iSeries

Steve Richter wrote:
 
> An example of this might be to intercept writes to a display device and 
> redirect the I/O
> to a web browser.

>All theory of course. The SEPT hook is something I always wanted to try but
>did not have the nerve for.  What is the worse that could happen?  A system
>crash??

Steve, I had the nerve! It kinda worked (my 'middleman' program was called 
instead of QWSGET and QWSPUT and did its thing, but it ended up as too much 
hassle - I was looking for a way I could change our web-enablement software 
package, but it's not going to work to sell something that forces customers to 
either use SST or at least to change some of their system values before 
restoring our software.

This basically what Fast/400 did, IIRC (hooking the SEPT to get at QT3REQIO), 
so it's certainly possible

 Also, my testing didn't end well, mainly because of the "gotcha" which Jean 
Michel pointed out (which I wasn't aware of):

>Nevertheless I advise to restore original SEPT Pointer into PCO before
>ending your job. Entries in WCBT are reused, and new jobs may be started
>with your own "sept".

Other people weren't so happy that my 'playing around' with my SEPT 
subsequently caused them problems...
 
Rory