Re: safe strcpy()?

From: Timo Sirainen (tssat_private)
Date: Tue Jan 28 2003 - 17:36:44 PST

  • Next message: Timo Sirainen: "Re: safe strcpy()?"

    On Wed, 2003-01-29 at 01:37, mlhat_private wrote:
    > Another library 'libslack' has a rich set of string functions:
    > 
    > 	http://libslack.org/manpages/str.3.html
    
    So it seems. That's probably one reason why people still keep using only
    libc stuff - requiring external libraries is annoying, distributing huge
    string+whatever libraries with your sources is annoying, and stripping
    them down to bare minimals is also annoying.
    
    I try to prevent mostly just write access buffer overflows, for that
    there's no need to rewrite all existing libc functions to work with yet
    another string type. If there's no secrets in process memory, there's no
    reason to worry about read access overflows more than there is to worry
    about bugs/crashes in general.
    



    This archive was generated by hypermail 2b30 : Wed Jan 29 2003 - 13:00:08 PST