Well, two mmap() and a signal handler. But no _practical_ way, anyway. :)
Exactly. @landley was talking about mitigation of gets() badness on the application side, not the implementation side.
-
-
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 …
End of conversation
New conversation -
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.