The following message is a courtesy copy of an article that has been posted to bit.listserv.ibm-main as well.
[EMAIL PROTECTED] (Paul Gilmartin) writes: > Some non-IBM systems can mark segments as I-fetch only and D-fetch > only. Does z/Series have this capability? It instantly traps on > wild-branch-into-data. Might also provide a guideline for cache > management. the stack smashing and buffer overflow (highly correlated with numerous c language programming environments) somewhat recently led to d-fetch hardware feature only ... aka countermeasure to various attacks hiding instructions inside incoming data. d-fetch only wouldn't fix programming problems with allowing long data/string structures to overlay things they shouldn't ... but it would at least prevent the execution of any hidden instructions. various flavors i-fetch (& execution) only hardware have been around for somewhat longer (execute-only as opposed to no-execute which is this later countermeasure to various vulnerabilities that have significantly higher occurance in c programming environments) old post discussing 360 key fetch/store protection and emerging d-fetch only (no-execute) ... http://www.garlic.com/~lynn/2005.html#5 [Lit.] Buffer overruns a few of the other no-execute posts (for stack smashing & buffer overrun vulnerabilities) http://www.garlic.com/~lynn/2004q.html#82 [Lit.] Buffer overruns http://www.garlic.com/~lynn/2005.html#0 [Lit.] Buffer overruns http://www.garlic.com/~lynn/2005.html#1 [Lit.] Buffer overruns http://www.garlic.com/~lynn/2005.html#3 [Lit.] Buffer overruns misc. posts with any mention of buffer overflow http://www.garlic.com/~lynn/subintegrity.html#overflow ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
