From owner-freebsd-sparc64@FreeBSD.ORG  Sat May 29 16:43:26 2004
Return-Path: <owner-freebsd-sparc64@FreeBSD.ORG>
Delivered-To: freebsd-sparc64@hub.freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP
	id 2AE5B16A4CE; Sat, 29 May 2004 16:43:26 -0700 (PDT)
Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21])
	by mx1.FreeBSD.org (Postfix) with ESMTP
	id 0B9FB43D41; Sat, 29 May 2004 16:43:26 -0700 (PDT)
	(envelope-from marius@FreeBSD.org)
Received: from freefall.freebsd.org (marius@localhost [127.0.0.1])
	i4TNhFv2037066;	Sat, 29 May 2004 16:43:15 -0700 (PDT)
	(envelope-from marius@freefall.freebsd.org)
Received: (from marius@localhost)
	by freefall.freebsd.org (8.12.11/8.12.11/Submit) id i4TNhF69037062;
	Sat, 29 May 2004 16:43:15 -0700 (PDT)
	(envelope-from marius)
Date: Sat, 29 May 2004 16:43:15 -0700 (PDT)
From: Marius Strobl <marius@FreeBSD.org>
Message-Id: <200405292343.i4TNhF69037062@freefall.freebsd.org>
To: hogsett@rr-spamd-3.csl.sri.com, marius@FreeBSD.org,
	freebsd-sparc64@FreeBSD.org
Subject: Re: sparc64/66622: ypwhich returns bogus data
X-BeenThere: freebsd-sparc64@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Porting FreeBSD to the Sparc <freebsd-sparc64.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-sparc64>,
	<mailto:freebsd-sparc64-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-sparc64>
List-Post: <mailto:freebsd-sparc64@freebsd.org>
List-Help: <mailto:freebsd-sparc64-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-sparc64>,
	<mailto:freebsd-sparc64-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sat, 29 May 2004 23:43:26 -0000

Synopsis: ypwhich returns bogus data

State-Changed-From-To: open->closed
State-Changed-By: marius
State-Changed-When: Sat May 29 16:37:13 PDT 2004
State-Changed-Why: 

This was fixed by tmm in src/include/rpcsvc/yp_prot.h revision 1.12.
As long as RELENG_5_2 is dedicated to security fixes it's unlikely
that a MFC will occur.

http://www.freebsd.org/cgi/query-pr.cgi?pr=66622