Linda Walsh <law@sgi.com>
> yoann@mandrakesoft.com wrote:
> > Linda Walsh <law@sgi.com> writes:
[...]
> > > buffer-stack overruns are one of the most common exploits.
> > > It seems making that more difficult to exploit would help. But a single
> > > brick does not build a wall. It's part of a wall.
> > A specialized library preloaded before the soft to monitor is much more
> > serious in this case, this library cauch call to dangerous function and
> > control the size of the destination buffer ( by walking throught the
> > stack) if the size which will be written is > than the dest buffer
> > size, the program is killed.
> Add that as well.
strncpy(3) and its ilk instead of strcpy(3) et al is standard
recomendation, take a look at the Secure-Programs-HOWTO for instance.
(BTW, how would this mythical function(s) know the buffer bounds just by
looking at the stack?) Real problem is that there are people doing string
copies by hand, or screw up the bound computation...
-- Dr. Horst H. von Brand mailto:vonbrand@inf.utfsm.cl Departamento de Informatica Fono: +56 32 654431 Universidad Tecnica Federico Santa Maria +56 32 654239 Casilla 110-V, Valparaiso, Chile Fax: +56 32 797513- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Sun Apr 23 2000 - 21:00:15 EST