From owner-freebsd-current@FreeBSD.ORG Mon Apr 28 19:57:51 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 408A737B401 for ; Mon, 28 Apr 2003 19:57:51 -0700 (PDT) Received: from gw.nectar.cc (gw.nectar.cc [208.42.49.153]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5FCAC43FDD for ; Mon, 28 Apr 2003 19:57:50 -0700 (PDT) (envelope-from nectar@celabo.org) Received: from madman.celabo.org (madman.celabo.org [10.0.1.111]) (using TLSv1 with cipher EDH-RSA-DES-CBC3-SHA (168/168 bits)) (Client CN "madman.celabo.org", Issuer "celabo.org CA" (verified OK)) by gw.nectar.cc (Postfix) with ESMTP id E2C084; Mon, 28 Apr 2003 21:57:49 -0500 (CDT) Received: by madman.celabo.org (Postfix, from userid 1001) id 3D75178C66; Mon, 28 Apr 2003 21:57:49 -0500 (CDT) Date: Mon, 28 Apr 2003 21:57:49 -0500 From: "Jacques A. Vidrine" To: NAKAJI Hiroyuki Message-ID: <20030429025749.GA49911@madman.celabo.org> Mail-Followup-To: "Jacques A. Vidrine" , NAKAJI Hiroyuki , freebsd-current@freebsd.org References: <20030428075916.GA53857@myhakas.internal> <20030428075916.GA53857@myhakas.internal> <20030428190209.A21656@dilbert.robbins.dropbear.id.au> <87of2rexxd.fsf@boggy.acest.tutrp.tut.ac.jp> <20030428174751.GA38323@madman.celabo.org> <86adeajfpe.fsf@xa12.heimat.gr.jp> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="YZ5djTAD1cGYuMQK" Content-Disposition: inline In-Reply-To: <86adeajfpe.fsf@xa12.heimat.gr.jp> X-Url: http://www.celabo.org/ User-Agent: Mutt/1.5.3i-ja.1 cc: freebsd-current@freebsd.org Subject: Re: Somethings still up with new NSS? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 29 Apr 2003 02:57:51 -0000 --YZ5djTAD1cGYuMQK Content-Type: text/plain; charset=us-ascii Content-Disposition: inline The problem is this: qpopper includes its own, buggy implementation of strlcpy. libc calls strlcpy, and gets qpopper's version. The qpopper version's return value is incorrect. That is really scary. Put the attached patch file in /usr/ports/mail/qpopper/files, and rebuild qpopper. This will disable the built-in strlcpy and strlcat, and it should then work. Cheers, -- Jacques Vidrine . NTT/Verio SME . FreeBSD UNIX . Heimdal nectar@celabo.org . jvidrine@verio.net . nectar@freebsd.org . nectar@kth.se --YZ5djTAD1cGYuMQK Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename="patch-common::string_util.c" *** common/string_util.c.orig Mon Apr 28 21:53:36 2003 --- common/string_util.c Mon Apr 28 21:54:06 2003 *************** *** 37,42 **** --- 37,43 ---- + #if 0 /* * Function: strlcpy * *************** *** 156,161 **** --- 157,163 ---- *dst = '\0'; return dstlen + ( src - strsource ) + strlen ( src ); } + #endif /* --YZ5djTAD1cGYuMQK--