Date: Wed, 26 Mar 2003 11:20:57 +0100 From: Simon Barner <barner@in.tum.de> To: "Jeremy C. Reed" <reed@reedmedia.net> Cc: freebsd-security@FREEBSD.ORG Subject: Re: what actually uses xdr_mem.c? Message-ID: <20030326102057.GC657@zi025.glhnet.mhn.de> In-Reply-To: <Pine.LNX.4.43.0303252144400.21019-100000@pilchuck.reedmedia.net> References: <Pine.LNX.4.43.0303252144400.21019-100000@pilchuck.reedmedia.net>
next in thread | previous in thread | raw e-mail | index | archive | help
--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--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030326102057.GC657>