Date: Thu, 15 Jul 1999 17:20:57 -0600 From: Warner Losh <imp@village.org> To: Garance A Drosihn <drosih@rpi.edu> Cc: Paul Hart <hart@iserver.com>, freebsd-security@FreeBSD.ORG Subject: Re: OpenBSD's strlcpy(3) and strlcat(3) Message-ID: <199907152320.RAA73691@harmony.village.org> In-Reply-To: Your message of "Thu, 15 Jul 1999 17:33:29 EDT." <v04011702b3b3f07b38ae@[128.113.24.47]> References: <v04011702b3b3f07b38ae@[128.113.24.47]>
next in thread | previous in thread | raw e-mail | index | archive | help
In message <v04011702b3b3f07b38ae@[128.113.24.47]> Garance A Drosihn writes: : What I wanted to do was have "estr" routines, where the destination : is specified as the starting point and the ending point of the area : available for the string (as two parameters). The routines would : return the position of the current string-terminator. So you could : do things like: : eos = estrcpy(dest, endp, src1); : eos = estrcat(eos, endp, src2); : eos = estrcat(eos, endp, src3); : and you could check for "string is full" by comparing 'eos' (the : return value) to 'endp' (which you'd already have). Strictly : speaking that won't work quite right in some cases, so the strlcpy : routines also have an advantage there. Yes. It would take a lot of talking and convincing to get me to support adding something other than strl* routines. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199907152320.RAA73691>