Really? Try getting rid of the tech then. Unplug the computers in the library and research using a card catalog. All written assignments must be typed on a typewriter. Tests, quizes and handouts will be typed or hand-written by the teacher and copied on a mimeograph machine. In science, all measurements will be made by hand and all lab reports will include hand-made calculations and hand drawn charts. To avoid having the kids calculate for 6 hours to generate a chart, they will be restricted to 4 measurements of their data.

If a child forgets an assignment, they'll have to call a friend, who will read it to them over the phone while they copy furiously (and incorrectly).

Video demonstrations or presentations in the classroom will go away. After all, it means finding it (in the library, on the card catalog, and hoping that we have such a tape), copying it on a VHS tape, wheeling the TV and VCR into the classroom (they're too bulky and expensive to put one in each room) and hoping that everything works.

Technology has had a HUGE effect on education, just as it has on everything else

I believe that most buffer overrun exploits work by overwriting a function's return address on the stack. These could be largely avoided by the compiler using either of two techniques. First, it could grow the stack into higher numbered addresses and store the return address first. Now if the code allows a buffer overrun, it will overrun the local variables and spill into the available stack space. In both cases, the chances of finding a function pointer are small. In contrast, if you grow the stack into smaller numbered addresses, then a buffer overrun has pretty much 100% chance to overwrite a code pointer (the return address).

The other technique is to use two stacks, one for the return addresses and another for the parameters/return values. Same idea though: move the return address out of the way of the overflowed buffer.

Personally, I stopped using the SETI@home screen saver years ago when I realized that it was burning an image in my screen - kind of the opposite of what a screen saver is supposed to do. Sure it won't happen now with my flat screen, but it pissed me off so much that I won't use it again.