At best that lets you safely abort the program on excess input; there's still no way to cleanly recover.
On the implementation side, the only mitigation is to have a memory-safe C implementation (highly nontrivial) so that it necessarily traps when gets() overflows.
-
-
Ah yes, all agreed. A memory-safe C implementation is what I'm working on. :-) (It promises to suck less than the others, too.)https://github.com/stephenrkell/libcrunch …
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.