From owner-freebsd-security Fri Jun 28 21: 8:23 2002 Delivered-To: freebsd-security@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4401F37B400 for ; Fri, 28 Jun 2002 21:08:20 -0700 (PDT) Received: from castle.jp.FreeBSD.org (castle.jp.FreeBSD.org [210.226.20.15]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3C7CD43E0A for ; Fri, 28 Jun 2002 21:08:19 -0700 (PDT) (envelope-from matusita@jp.FreeBSD.org) Received: from localhost (localhost [::1]) by castle.jp.FreeBSD.org (8.11.6+3.4W/8.11.3) with ESMTP/inet6 id g5T48Hn48826 for ; Sat, 29 Jun 2002 13:08:17 +0900 (JST) (envelope-from matusita@jp.FreeBSD.org) X-User-Agent: Mew/1.94.2 XEmacs/21.5 (bamboo) X-FaceAnim: (-O_O-)(O_O- )(_O- )(O- )(- -)( -O)( -O_)( -O_O)(-O_O-) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Dispatcher: imput version 20000228(IM140) Lines: 10 From: Makoto Matsushita To: security@FreeBSD.org Subject: libc resolver fix: can we applied to 3-stable or before? Date: Sat, 29 Jun 2002 13:06:07 +0900 Message-Id: <20020629130607U.matusita@jp.FreeBSD.org> Sender: owner-freebsd-security@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Simple question: Is our 3-stable libc vulnerable? If so, can we apply the same patch to RELENG_3 also? If 3-stable libc is vulnerable, our compat3x/libc.so.3.uu bundled with 4-stable (and 5-stable in the future) is also vulnerable, and it would be good to fix. Note that same stories are also applied to libc of 2.2-stable or before. -- - Makoto `MAR' Matsushita To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message