From owner-freebsd-security@FreeBSD.ORG Wed Mar 26 02:21:03 2003 Return-Path: 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 6883B37B404 for ; Wed, 26 Mar 2003 02:21:03 -0800 (PST) Received: from mailout.informatik.tu-muenchen.de (mailout.informatik.tu-muenchen.de [131.159.0.5]) by mx1.FreeBSD.org (Postfix) with ESMTP id E87D143FBF for ; Wed, 26 Mar 2003 02:21:00 -0800 (PST) (envelope-from barner@in.tum.de) Received: from mailrelay1.informatik.tu-muenchen.de (mailrelay1.informatik.tu-muenchen.de [131.159.254.5]) by mailout.informatik.tu-muenchen.de (Postfix) with ESMTP id 093E4625C; Wed, 26 Mar 2003 11:21:00 +0100 (MET) Received: from mail.informatik.tu-muenchen.de (mail.informatik.tu-muenchen.de [131.159.0.26]) by mailrelay1.informatik.tu-muenchen.de (Postfix) with ESMTP id EF7667944; Wed, 26 Mar 2003 11:20:59 +0100 (MET) Received: from zi025.glhnet.mhn.de (unknown [129.187.19.157]) by mail.informatik.tu-muenchen.de (Postfix) with ESMTP id AC4FC6CB10; Wed, 26 Mar 2003 11:20:59 +0100 (MET) Received: by zi025.glhnet.mhn.de (Postfix, from userid 1000) id 7C64436D25; Wed, 26 Mar 2003 11:20:58 +0100 (CET) Date: Wed, 26 Mar 2003 11:20:57 +0100 From: Simon Barner To: "Jeremy C. Reed" Message-ID: <20030326102057.GC657@zi025.glhnet.mhn.de> References: Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="zCKi3GIZzVBPywwA" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.4i X-Spam-Status: No, hits=-31.7 required=5.0 tests=AWL,IN_REP_TO,PGP_SIGNATURE_2,QUOTED_EMAIL_TEXT,REFERENCES, REPLY_WITH_QUOTES,USER_AGENT_MUTT autolearn=ham version=2.50 X-Spam-Level: X-Spam-Checker-Version: SpamAssassin 2.50 (1.173-2003-02-20-exp) cc: freebsd-security@FREEBSD.ORG Subject: Re: what actually uses xdr_mem.c? X-BeenThere: freebsd-security@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Security issues [members-only posting] List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 26 Mar 2003 10:21:04 -0000 --zCKi3GIZzVBPywwA Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hi Jeremy, > The recent XDR fixes the xdrmem_getlong_aligned(), > xdrmem_putlong_aligned(), xdrmem_getlong_unaligned(), > xdrmem_putlong_unaligned(), xdrmem_getbytes(), and/or xdrmem_putbytes() > functions, but it is difficult to know what uses these (going backwards > manually). >=20 > For example, a simple MD5 (of binaries before and after) shows many > changes that are probably irrelevant. It is hard to tell if any static > tools even use those changes; maybe mount_nfs and umount. And maybe > /usr/lib/librpcsvc*. I would not rely on the binaries to find out, which programs make use of the above functions. That's one of the advantages of an open source os ;-) Something like cd /usr/src grep -rl 'xdrmem_getlong_aligned' * will print all the files that contain the string 'xdrmem_getlong_aligned'. = Based on the path name of those file, you will be able to find out which programs= use the xdr* functions. HTH, Simon --zCKi3GIZzVBPywwA Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Digital signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (FreeBSD) iD8DBQE+gX8JCkn+/eutqCoRAqIuAJ4j44ly1m7bZ/HLzZT7N2guqldT7gCgsHTg DpQs7uF/X4L7aJZBVebirkc= =kuPP -----END PGP SIGNATURE----- --zCKi3GIZzVBPywwA--