From owner-freebsd-security Thu Jul 15 17:17:52 1999 Delivered-To: freebsd-security@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 60B9C15724 for ; Thu, 15 Jul 1999 17:17:47 -0700 (PDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id SAA29682; Thu, 15 Jul 1999 18:17:46 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id SAA01078; Thu, 15 Jul 1999 18:17:45 -0600 (MDT) Message-Id: <199907160017.SAA01078@harmony.village.org> To: Sheldon Hearn Subject: Re: OpenBSD's strlcpy(3) and strlcat(3) Cc: Brett Glass , Paul Hart , freebsd-security@FreeBSD.ORG In-reply-to: Your message of "Fri, 16 Jul 1999 02:12:35 +0200." <81297.932083955@axl.noc.iafrica.com> References: <81297.932083955@axl.noc.iafrica.com> Date: Thu, 15 Jul 1999 18:17:45 -0600 From: Warner Losh Sender: owner-freebsd-security@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In message <81297.932083955@axl.noc.iafrica.com> Sheldon Hearn writes: : Reality check: we're talking about portability here. If we take these : functions into our own libc, we really should make them work as expected : on other platforms. However, there's nothing to stop us extending them : beyond those expectations. No. They will be 100% compatible, or not imported. No extensions that could bite people when porting *TO* OpenBSD. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message