Since a lot of unwanted doors (read security vulnerability) are created as a result of buffer overflows (blame it on who ever you want to: CPU manufacturers, compiler designers, language architects, etc) is it possible to create a kernel-level watchdog that keeps an eye on stack tampering?
Forget MIS, CIS, IT majors - couldn't make it in business and their computer knowledge is a joke.
Forget anybody with Certified/overnight (read 300 pages and you are an expert too) degrees.
Forget "undergraduate" only CS/CompEng majors - They are in it only for the money.
Do look into graduate Cs/CompEng. Do look for graduate math/physics majors working in computer labs.
Slashdot Mirror
Since a lot of unwanted doors (read security vulnerability) are created as a result of buffer overflows (blame it on who ever you want to: CPU manufacturers, compiler designers, language architects, etc) is it possible to create a kernel-level watchdog that keeps an eye on stack tampering?
Forget MIS, CIS, IT majors - couldn't make it in business and their computer knowledge is a joke. Forget anybody with Certified/overnight (read 300 pages and you are an expert too) degrees. Forget "undergraduate" only CS/CompEng majors - They are in it only for the money. Do look into graduate Cs/CompEng. Do look for graduate math/physics majors working in computer labs.