bdonlan: > Use an interpreted language. They'll prevent buffer overflows and you can > unimplement unallowed functions.
Buffer overflows are the worst offender, but there are plenty of other ways that programs can be tricked into doing things they never should be doing. Ruling out those possibilities in advance is worthwhile. We _have_ this information, and we should _use_ it. Not using our knowledge that (say) MPlayer needn't access any file but this one and that one is simply negligence, in my opinion. And frankly, it is unlikely that MPlayer is going to be rewritten in Perl any time soon. The capabilities scheme I propose can be put to use immediately, with a minimum of effort, on all the myriad bad code that people have to use. > Just mark the code read-only, and the stack non-executable. That would be ideal, I agree, but I get the impression that those features have not been implemented yet on x86. _______________________________________________ devl mailing list [EMAIL PROTECTED] http://hawk.freenetproject.org:8080/cgi-bin/mailman/listinfo/devl
